On Thu, 29 Nov 2012, Andy Green wrote: > However I think what you're saying about binding to hub power is good. > The hub ports are not devices, but it would be possible to bind an asset > array to them and make the pre- and post- code functions. In the 3.6 kernel, hub ports are not devices. In 3.7 they are -- that is, each hub port has its own struct device. > I think it will be possible to address objections around the "pathiness" > by being able to seed the path match with a platform_device pointer > (there exists in the board file time a platform_device for ehci-omap.0 > ...) and just matching the remainder on a single usb device's name, like > "*-1.1-1". Can you think of a way to do this without checking for a match every time a new device is registered? For instance, in this case it would be preferable to do this match only for descendants of ehci-omap.0. To match the port device, the string would have to be something like "*-0:1.0/port2". In fact, if the match were anchored at the end of the string, we wouldn't need the wildcard at all -- at least, not in this case. The string could simply be "-0:1.0/port2". But that's only if the match is restricted to devices below ehci-omap.0. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
