On Tue, Aug 20, 2013 at 12:01 AM, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Mon, Aug 19, 2013 at 08:17:53PM +0800, Ming Lei wrote: >> On Sat, Aug 17, 2013 at 9:29 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > >> > Aong those lines, I would like to point out that the device concept >> > embodied in the kernel's data structures can be pretty thin. For >> > example, it might be little more than a port number or bus address. > >> Maybe the principle behind drivers/usb/core/usb-acpi.c is helpful >> for the problem, and DT may refer to ACPI to describe on-board >> USB devices, and the way to retrieve platform data too. > > I can't parse this at all well - why would DT want to refer to ACPI, do > you mean people may wish to look at the code as an example? As Grant I mean usb-acpi provides one approach to retrieve platform data for USB device during device enumeration, and the idea might be helpful for you to implement similar things based on DT. > noted DT already has some mechanisms for enumerable buses which looking > at the code appears to be broadly what that's doing. If the mechanism is ready now, so looks you might post code for review and discussion? Thanks, -- Ming Lei -- 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
