dm: pinctrl: introduce PINCONF_RECURSIVE option
authorPatrick Delaunay <patrick.delaunay@st.com>
Fri, 2 Aug 2019 12:48:00 +0000 (14:48 +0200)
committerSimon Glass <sjg@chromium.org>
Tue, 15 Oct 2019 14:40:03 +0000 (08:40 -0600)
commite878b53a79d1a4f06c7c03d706da6b2993e8ff41
treee0b9a6ad983d31589cf39fd7a429ac2b72faad98
parent52edfed65de967a86983a55c51ba0727090efc43
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.

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>
drivers/pinctrl/Kconfig
drivers/pinctrl/pinctrl-uclass.c