diff options
author | Amelie Delaunay <amelie.delaunay@st.com> | 2019-11-04 11:09:08 +0100 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2019-11-07 10:06:46 +0100 |
commit | 63e006c107ff4235d2a8fd52704f283d23642537 (patch) | |
tree | 7ec9ff9b2294bfdaf51fd5d0382aad30aede73fa /net/wimax/debugfs.c | |
parent | Merge tag 'intel-pinctrl-fixes-v5.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel into fixes (diff) | |
download | linux-dev-63e006c107ff4235d2a8fd52704f283d23642537.tar.xz linux-dev-63e006c107ff4235d2a8fd52704f283d23642537.zip |
pinctrl: stmfx: fix valid_mask init sequence
With stmfx_pinctrl_gpio_init_valid_mask callback, gpio_valid_mask was used
to initialize gpiochip valid_mask for gpiolib. But gpio_valid_mask was not
yet initialized. gpio_valid_mask required gpio-ranges to be registered,
this is the case after gpiochip_add_data call. But init_valid_mask
callback is also called under gpiochip_add_data. gpio_valid_mask
initialization cannot be moved before gpiochip_add_data because
gpio-ranges are not registered.
So, it is not possible to use init_valid_mask callback.
To avoid this issue, get rid of valid_mask and rely on ranges.
Fixes: da9b142ab2c5 ("pinctrl: stmfx: Use the callback to populate valid_mask")
Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
Link: https://lore.kernel.org/r/20191104100908.10880-1-amelie.delaunay@st.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'net/wimax/debugfs.c')
0 files changed, 0 insertions, 0 deletions