Am Mittwoch, den 30.11.2016, 15:54 +0200 schrieb Vladimir Zapolskiy: > Hello Lucas, > > On 11/30/2016 01:50 PM, Lucas Stach wrote: > > DDC buses are manually managed by their consumers to communicate > > with the display. There is no need to try to populate OF childs. > > > > This gets rid of the device create failed warning caused by the > > core trying to populate a DDC bus below a OF device, which has > > other childs nodes, that aren't i2c devices. > > what kind of devices on a DDC bus represended by children nodes > do you reference here? None. The device registering the DDC i2c adapter might have an of_node. The children of this device are not i2c devices, but for example port nodes for the of_graph binding. The same issue can be worked around if we make it explicit by placing an "i2c-bus" subnode with no children into the parent device OF node. But as the OF probing of devices on a DDC bus just doesn't make sense I figured it would be good to just skip all this. Regards, Lucas -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
