diff options
| author | Stephen Boyd <sboyd@codeaurora.org> | 2018-03-23 17:34:53 +0100 |
|---|---|---|
| committer | Linus Walleij <linus.walleij@linaro.org> | 2018-03-27 15:34:25 +0200 |
| commit | 691bf5d5a7bfedc60b7218f4d9b915bf356df767 (patch) | |
| tree | 074506c16494fc907fb4e5e9e194e8876ad69f27 /drivers/gpio | |
| parent | gpiolib: Support 'gpio-reserved-ranges' property (diff) | |
| download | linux-691bf5d5a7bfedc60b7218f4d9b915bf356df767.tar.xz linux-691bf5d5a7bfedc60b7218f4d9b915bf356df767.zip | |
pinctrl: qcom: Don't allow protected pins to be requested
Some qcom platforms make some GPIOs or pins unavailable for use
by non-secure operating systems, and thus reading or writing the
registers for those pins will cause access control issues and
reset the device. With a DT/ACPI property to describe the set of
pins that are available for use, parse the available pins and set
the irq valid bits for gpiolib to know what to consider 'valid'.
This should avoid any issues with gpiolib. Furthermore, implement
the pinmux_ops::request function so that pinmux can also make
sure to not use pins that are unavailable.
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Tested-by: Timur Tabi <timur@codeaurora.org>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio')
0 files changed, 0 insertions, 0 deletions