Re: Thoughts on ASOC v2 driver architecture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mark Brown wrote:

> Right, but you could not then idiomatically have a device tree entry
> saying something to the effect of "This board has a Frobnitz 2000 with
> control line 1 connected to GPIO4 and control line 2 connected to GPIO5"

Yes.

> which would register the presence of this other device (in the same way
> as you have an entry for an I2C device)?

I'm still not sure I understand.  I2C devices are represented by complete nodes
under the I2C adapter node.  The file fsl_soc.c scans each I2C adapter node, and
enumerates every child node under the adapter node.  It creates I2C platform
devices this way.

I'm not sure how we could use this model for ASoC.  There is no "ASoC adapter
node" in the device tree, because there is no ASoC adapter.

-- 
Timur Tabi
Linux kernel developer at Freescale
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux