U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Delaunay <patrick.delaunay@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pinctrl: Kconfig: remove duplicated nodes
Date: Mon, 21 Oct 2019 15:07:54 +0200	[thread overview]
Message-ID: <20191021130754.32466-1-patrick.delaunay@st.com> (raw)

Remove the duplicated configs introduced when the same patch is
applied twice times:
- commit e878b53a79d1 ("dm: pinctrl: introduce PINCONF_RECURSIVE
  option")
- commit c20851b3d850 ("dm: pinctrl: introduce PINCONF_RECURSIVE
  option")


Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
---

 drivers/pinctrl/Kconfig | 25 -------------------------
 1 file changed, 25 deletions(-)

diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
index 6b41f66a86..deee92411c 100644
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
@@ -75,22 +75,6 @@ config PINCONF_RECURSIVE
 	  configuration; you can save memory footprint when this feature is
 	  no needed.
 
-config PINCONF_RECURSIVE
-	bool "Support recursive binding for pin configuration nodes"
-	depends on PINCTRL_FULL
-	default n if ARCH_STM32MP
-	default y
-	help
-	  In the Linux pinctrl binding, the pin configuration nodes need not be
-	  direct children of the pin controller device (may be grandchildren for
-	  example). It is define is each individual pin controller device.
-	  Say Y here if you want to keep this behavior with the pinconfig
-	  u-class: all sub are recursivelly bounded.
-	  If the option is disabled, this behavior is deactivated and only
-	  the direct children of pin controller will be assumed as pin
-	  configuration; you can save memory footprint when this feature is
-	  no needed.
-
 config SPL_PINCTRL
 	bool "Support pin controllers in SPL"
 	depends on SPL && SPL_DM
@@ -145,15 +129,6 @@ config SPL_PINCONF_RECURSIVE
 	  This option is an SPL-variant of the PINCONF_RECURSIVE option.
 	  See the help of PINCONF_RECURSIVE for details.
 
-config SPL_PINCONF_RECURSIVE
-	bool "Support recursive binding for pin configuration nodes in SPL"
-	depends on SPL_PINCTRL_FULL
-	default n if ARCH_STM32MP
-	default y
-	help
-	  This option is an SPL-variant of the PINCONF_RECURSIVE option.
-	  See the help of PINCONF_RECURSIVE for details.
-
 if PINCTRL || SPL_PINCTRL
 
 config PINCTRL_AR933X
-- 
2.17.1

             reply	other threads:[~2019-10-21 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 13:07 Patrick Delaunay [this message]
2019-10-21 15:44 ` [U-Boot] [PATCH] pinctrl: Kconfig: remove duplicated nodes Anatolij Gustschin
2019-10-21 17:26 ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2019-10-22  7:51 Patrick DELAUNAY

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191021130754.32466-1-patrick.delaunay@st.com \
    --to=patrick.delaunay@st.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox