Searched hist:fab50c1fafdacbccbd42aeaf7b1aef1af07af78e (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/drivers/pinctrl/ |
| H A D | pinctrl-uclass.c | fab50c1fafdacbccbd42aeaf7b1aef1af07af78e Fri Aug 02 12:48:00 UTC 2019 Patrick Delaunay <patrick.delaunay@st.com> UPSTREAM: dm: pinctrl: introduce PINCONF_RECURSIVE option
In the Linux pinctrl binding, the pin configuration nodes don't need to
be direct children of the pin controller device (may be grandchildren for
example). This behavior is managed with the pinconfig u-class which
recursively bind all the sub-node of the pin controller.
But for some binding (when pin configuration is only children of pin
controller) that is not necessary. U-Boot can save memory and reduce
the number of pinconf instance when this feature is deactivated
(for arch stm32mp for example for SPL).
This patch allows to control this feature with a new option
CONFIG_PINCONF_RECURSIVE when it is possible for each individual
pin controller device.
Change-Id: I0c8c362c14595cea95cc4e0f647df7f0451c4cab
Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
(cherry picked from commit c20851b3d850dd859f202d2395e8dde0fc81c1ce)
Signed-off-by: Cody Xie <cody.xie@rock-chips.com>
|
| H A D | Kconfig | fab50c1fafdacbccbd42aeaf7b1aef1af07af78e Fri Aug 02 12:48:00 UTC 2019 Patrick Delaunay <patrick.delaunay@st.com> UPSTREAM: dm: pinctrl: introduce PINCONF_RECURSIVE option
In the Linux pinctrl binding, the pin configuration nodes don't need to
be direct children of the pin controller device (may be grandchildren for
example). This behavior is managed with the pinconfig u-class which
recursively bind all the sub-node of the pin controller.
But for some binding (when pin configuration is only children of pin
controller) that is not necessary. U-Boot can save memory and reduce
the number of pinconf instance when this feature is deactivated
(for arch stm32mp for example for SPL).
This patch allows to control this feature with a new option
CONFIG_PINCONF_RECURSIVE when it is possible for each individual
pin controller device.
Change-Id: I0c8c362c14595cea95cc4e0f647df7f0451c4cab
Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
(cherry picked from commit c20851b3d850dd859f202d2395e8dde0fc81c1ce)
Signed-off-by: Cody Xie <cody.xie@rock-chips.com>
|