On Fri, Nov 02, 2012 at 10:34:21AM +0800, Bo Shen wrote:

On 11/1/2012 22:43, Mark Brown wrote:

quoted

On Wed, Oct 31, 2012 at 03:26:59PM +0800, Bo Shen wrote:

quoted

quoted

+dai: dai {
+	compatible = "atmel,atmel-ssc-dai";
+	atmel,dai-master = <&ssc0>;
+};

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,

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

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.

Your quote appears to have deleted the bit of my mail where I told you
how to fix this.  Is there something unclear in my suggestion that the
machine driver directly reference the SSC node?
-------------- 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/20121102/d8cbe679/attachment.sig>