Searched hist:"0202 cbd2215769d41be3259eb6bd9d164044e50b" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/drivers/pinctrl/ |
| H A D | pinctrl-uclass.c | 0202cbd2215769d41be3259eb6bd9d164044e50b 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: I2c8a80186e9fda512e1e2c32c8cca104831e0da4
Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Fixed CONFIG_IF_ENABLED() condition, added __maybe_unused:
Signed-off-by: Simon Glass <sjg@chromium.org>
(cherry picked from commit e878b53a79d1a4f06c7c03d706da6b2993e8ff41)
Signed-off-by: Cody Xie <cody.xie@rock-chips.com>
|
| H A D | Kconfig | 0202cbd2215769d41be3259eb6bd9d164044e50b 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: I2c8a80186e9fda512e1e2c32c8cca104831e0da4
Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Fixed CONFIG_IF_ENABLED() condition, added __maybe_unused:
Signed-off-by: Simon Glass <sjg@chromium.org>
(cherry picked from commit e878b53a79d1a4f06c7c03d706da6b2993e8ff41)
Signed-off-by: Cody Xie <cody.xie@rock-chips.com>
|