On Fri, Aug 05, 2016 at 06:59:08PM +0100, Mark Brown wrote: > On Fri, Aug 05, 2016 at 06:04:50PM +0100, Russell King - ARM Linux wrote: > > On Fri, Aug 05, 2016 at 05:59:59PM +0100, Mark Brown wrote: > > > > We do have some stuff in there in order to handle MFDs - they'll > > > instantiate a Linux-internal virtual platform device as a child of the > > > DT device that represents the device as a whole. We're definitely not > > > expecting to find anything for parentless platform devices though, it's > > > only done if the ASoC level device has no of_node and the parent does. > > > And if we make the hdmi-codec device a child of the I2C device which > > does have an of-node, what will happen? > > It'll pick up that as the DT device to hang things off which I'd expect > to be the desired outcome given that this is a very similar situation to > the MFD situation. I've not been following the full thread so there is > probably context I'm missing here... Okay, and that sounds to me like a very reasonable thing to want to happen - so that the audio side can be clearly identified as being coupled with the video side. So, I'm not seeing a problem with my suggestion... I'm actually more reasons why it's a good thing to want. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
