Commit af6c235d authored by Linus Walleij's avatar Linus Walleij

gpio: discourage passing base to gpio_chip

Passing a fixed base in struct gpio_chip is done for legacy
systems that cannot handle dynamic allocation. Discourage this
behaviour in the kerneldoc.
Acked-by: default avatarAlexandre Courbot <acourbot@nvidia.com>
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
parent 25e4fe92
...@@ -42,8 +42,12 @@ struct seq_file; ...@@ -42,8 +42,12 @@ struct seq_file;
* @dbg_show: optional routine to show contents in debugfs; default code * @dbg_show: optional routine to show contents in debugfs; default code
* will be used when this is omitted, but custom code can show extra * will be used when this is omitted, but custom code can show extra
* state (such as pullup/pulldown configuration). * state (such as pullup/pulldown configuration).
* @base: identifies the first GPIO number handled by this chip; or, if * @base: identifies the first GPIO number handled by this chip;
* negative during registration, requests dynamic ID allocation. * or, if negative during registration, requests dynamic ID allocation.
* DEPRECATION: providing anything non-negative and nailing the base
* base offset of GPIO chips is deprecated. Please pass -1 as base to
* let gpiolib select the chip base in all possible cases. We want to
* get rid of the static GPIO number space in the long run.
* @ngpio: the number of GPIOs handled by this controller; the last GPIO * @ngpio: the number of GPIOs handled by this controller; the last GPIO
* handled is (base + ngpio - 1). * handled is (base + ngpio - 1).
* @desc: array of ngpio descriptors. Private. * @desc: array of ngpio descriptors. Private.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment