Hi Mark,
On 05/08/2012 04:41 PM, Mark Brown wrote:
On Tue, May 08, 2012 at 03:42:41PM +0300, Peter Ujfalusi wrote:
On 05/08/2012 03:26 PM, Mark Brown wrote:
Why are we loading MFD components using device tree? It seems like we're doing something very wrong if we need people to explicitly write
I have based the twl6040 DT structure on the already existing twl4030, twl6030 MFD parts.
This really isn't relevant to the issue...
I thought it was...
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. 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?