Re: RFC: New Driver Model for 2.5

Re: RFC: New Driver Model for 2.5

[David Brownell]

There seems to be a lot of agreement that having some
explicit representation of the device tree will help do the
power management better.  That's something USB has
so far not done; there's no current hook from the host
controller drivers (HCDs) to power manage devices.
(But then, there's no HCD layer yet either.  Each HCD
duplicates a lot of code, though there's work afoot to
change that.)

It might be appropriate to have, for example, the USB
portions of the device tree handle hub parent/child style
relationships.  Hubs can't be resumed after their children,
and so on.  Likewise it's no good telling devices they
should attempt remote wakeups unless all the hubs they
are connected to can wake up their parent devices, too;
no bus-powered hubs can be in that part of the tree.

And better standards for device naming and identification
are IMO good ... that'll improve diagnostics, and with a
bit of care we can finally have reasonably "stable" names.
Again, with USB the hub parent/child relationships are
more stable than the bus addresses that get assigned;
they can be used to distinguish the numerous devices
that don't have serial numbers (or for which the serial
numbers aren't really unique).

- Dave