On Thu, Nov 09, 2017 at 06:07:15PM +0100, Johan Hovold wrote: > This series adds support for representing USB interfaces in device tree > by implementing support for "interface nodes" and "combined nodes" from > the OF specification. > > This is needed to be able to describe non-discoverable properties of > permanently attached USB devices and their interfaces such as any > i2c-clients connected to a USB-i2c bridge (e.g. the dln2 mfd) or, > eventually, devices connected to usb-serial converters (to be used with > serdev). In the original OF binding, the firmware dynamically generated the tree for the active configuration AIUI. That doesn't really fit for the (mostly) static FDT usage and why we stopped at the device level. So how do we handle multiple configs? Or can we assume that if say the I2C bus is used, then there's only one config and interface that can use it? Rob -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
