[alsa-devel] [PATCH] ASoC: twl6040: Support for DT

Mark Brown broonie at opensource.wolfsonmicro.com
Wed May 9 15:35:12 CEST 2012

On Wed, May 09, 2012 at 03:01:23PM +0300, Peter Ujfalusi wrote:
> On 05/08/2012 04:41 PM, Mark Brown wrote:
> > On Tue, May 08, 2012 at 03:42:41PM +0300, Peter Ujfalusi wrote:

> >> Also without a DT entry I will not have a way to use phandle to
> >> connect the codec in the machine driver.

> > Of course you do!  There's going to be a device tree entry for the
> > chip, things can point at this perfectly happily.

> That's true but what can I do with that in the ASoC machine driver?
> The chip driver is _not_ the codec driver.

This really doesn't seem like it should be at all hard to resolve...

> I can craft the pdata for the MFD child devices out from the DT
> information but then the child devices will have no dev.of_node since
> they were not probed via OF.  So I would have not phandle for the
> codec to be used to define the dai-link connection within the sound
> dts section.

> Am I missing something here?

Clearly.  This is all very circular.  Obviously if you're intent on
using a phandle specific to the MFD child then you need to have that in
the device tree but this is because you're making the child devices
externally visible...  Clearly if we're not going to use the MFD
subdevices in the DT then the links ought to reference the chip.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20120509/24320c27/attachment.sig 

More information about the Alsa-devel mailing list