On 10/09/2013 08:01 AM, Linus Walleij wrote:

On Wed, Oct 9, 2013 at 3:28 PM, Christian Ruppert
[off-list ref] wrote:

quoted

On Wed, Oct 09, 2013 at 01:58:35PM +0200, Linus Walleij wrote:

quoted

On Tue, Oct 8, 2013 at 2:25 PM, Christian Ruppert
[off-list ref] wrote:

...

quoted

Obviously, a driver (no matter for which OS) must be aware of
this hardware property so it can decide which value to write to which
register in order to control the pin mux. If we don't want to split (or
worse: duplicate) that information in the driver and device tree, I see
two alternatives.
1. Define register offsets, masks and register values and the list of
   pins controlled by those register/value pairs in the device tree.

This is not a viable alternative of course.

Cough. pinctrl-single. Cough.