On Tue, Nov 06, 2012 at 01:39:12PM +0800, Bo Shen wrote:

On 11/5/2012 13:25, Bo Shen wrote:

Note that there's less than 24 hours between these two mails...

quoted

Sorry for misunderstand. I split your e-mail into two parts. May be you
miss some parts of my e-mail. You can check the last mail from me. Or
check the following fully quote.

Anyway, I will sent out a RFC patch series (which will be v3) which
register dai and platform directly in Linux.

quoted

quoted

This seems to be a purely virtual device which remaps the SSC onto the
Linux audio subsystem?  If that is the case then it shouldn't appear in
the device tree,

quoted

Yes. This is a purely virtual device. I add this as to the following
reason.

quoted

In our case, the ssc can connect to audio codec, DAC and other devices.
In order to avoid duplicate the code, so keep ssc as a library, register
it directly in Linux and use remap method to let it work onto other
different subsystem.

The whole point here is that this remapping shouldn't appear in the
device tree since it's a purely Linux internal issue, the code that uses
the SSC should have a reference to the SSC and then do whatever
remapping is required.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121106/b4fff9ac/attachment.sig>