On Wed, Nov 23, 2011 at 1:28 AM, Stephen Warren [off-list ref] wrote:
Describing the HW doesn't necessarily
mean that each device needs to describe what pinmux pins it uses; one
could quite easily have the pinmux describe what settings the various
pins should have and which drivers will use those pins. That would map
very well to the pinctrl subsystem's mapping table, and at least Tegra's
existing pinmux tables, which are both just a big array of settings which
end up getting provided to drivers.
That sounds true. It's also something that is cleanly cut out as a very
well defined and abstract piece of hardware information to live in the
device tree and which would be useful for any OS using DT.
I'd have to see the device trees and corresponding map bindings
before I understand it fully though.
Just my €0.01
Linus Walleij