diff options
author | Linus Walleij <linus.walleij@linaro.org> | 2012-02-01 21:02:47 +0400 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2012-02-01 22:42:35 +0400 |
commit | 9dfac4fd7f8cdcdf734dff2ccc7ca467f53f1cfd (patch) | |
tree | 6a9ee37b2aac4b288c85387d83310e5f9cd9108e /Documentation | |
parent | 8dc6ae4d448758a30cf5fa822d6fe6f4e15a04c6 (diff) | |
download | linux-9dfac4fd7f8cdcdf734dff2ccc7ca467f53f1cfd.tar.xz |
pinctrl: delete raw device pointers in pinmux maps
After discussion with Mark Brown in an unrelated thread about
ADC lookups, it came to my knowledge that the ability to pass
a struct device * in the regulator consumers is just a
historical artifact, and not really recommended. Since there
are no in-kernel users of these pointers, we just kill them
right now, before someone starts to use them.
Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/pinctrl.txt | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt index 150fd3833d0b..14aecd2b2dbc 100644 --- a/Documentation/pinctrl.txt +++ b/Documentation/pinctrl.txt @@ -805,10 +805,7 @@ must match a function provided by the pinmux driver handling this pin range. As you can see we may have several pin controllers on the system and thus we need to specify which one of them that contain the functions we wish -to map. The map can also use struct device * directly, so there is no -inherent need to use strings to specify .dev_name or .ctrl_dev_name, these -are for the situation where you do not have a handle to the struct device *, -for example if they are not yet instantiated or cumbersome to obtain. +to map. You register this pinmux mapping to the pinmux subsystem by simply: |