summaryrefslogtreecommitdiff
path: root/arch/mips/boot/dts/ingenic/ci20.dts
diff options
context:
space:
mode:
authorNikita Yushchenko <nikita.yoush@cogentembedded.com>2017-05-11 23:02:11 +0300
committerLinus Walleij <linus.walleij@linaro.org>2017-05-22 17:05:44 +0200
commit7f0ff06c1cec4bb2fc039b41943fd23245e3d0ca (patch)
tree9dd412dd0e117a7b9084f2b0d69227a5f085c71e /arch/mips/boot/dts/ingenic/ci20.dts
parent5586ee4191219f74632ad6e527c46d1c3d9cdf3e (diff)
pinctrl: When claiming hog, skip maps not served by same device
When pinctrl device registers, it automatically claims hogs, that is, maps that pinctrl device serves for itself. It is possible that in addition to SoC's pinctrl device, other pinctrl devices get registered. E.g. some gpio expander devies are registered as pinctrl devices. For such devices, pinctrl maps could be defined that set up SoC's pins (e.g. interrupt pin for gpio expander). Such a map will have target device set to gpio expander. Here is device tree snippet that causes this scenario: &i2c0 { sx1503@20 { compatible = "semtech,sx1503q"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_sx1503_20>; ... }; }; ... &iomuxc { pinctrl_sx1503_20: pinctrl-sx1503-20 { fsl,pins = < VF610_PAD_PTB1__GPIO_23 0x219d >; }; }; Such a map will have target device set to gpio expander. However is not a hog, it is a regular map that is claimed by core before gpio expander device is probed. Thus when looking for hogs, it is not enough to check that map's target device is set to pinctrl device being registered. Need also check that map's control device is also set to the same. Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com> Acked-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'arch/mips/boot/dts/ingenic/ci20.dts')
0 files changed, 0 insertions, 0 deletions