From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Julian Braha" <julianbraha@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Joel Stanley" <joel@jms.id.au>
Cc: linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
fazilyildiran@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pinctrl: aspeed: fix unmet dependencies on MFD_SYSCON for PINCTRL_ASPEED
Date: Wed, 03 Nov 2021 09:16:30 +1030 [thread overview]
Message-ID: <3fc55e2b-05cb-438d-b1cb-0d62f26c5411@www.fastmail.com> (raw)
In-Reply-To: <20211029212157.14230-1-julianbraha@gmail.com>
On Sat, 30 Oct 2021, at 07:51, Julian Braha wrote:
> When PINCTRL_ASPEED_G* is selected,
> and MFD_SYSCON is not selected,
> Kbuild gives the following warnings:
>
> WARNING: unmet direct dependencies detected for PINCTRL_ASPEED
> Depends on [n]: PINCTRL [=y] && (ARCH_ASPEED [=n] || COMPILE_TEST
> [=y]) && OF [=y] && MFD_SYSCON [=n]
> Selected by [y]:
> - PINCTRL_ASPEED_G4 [=y] && PINCTRL [=y] && (MACH_ASPEED_G4 [=n] ||
> COMPILE_TEST [=y]) && OF [=y]
>
> WARNING: unmet direct dependencies detected for PINCTRL_ASPEED
> Depends on [n]: PINCTRL [=y] && (ARCH_ASPEED [=n] || COMPILE_TEST
> [=y]) && OF [=y] && MFD_S>
> Selected by [y]:
> - PINCTRL_ASPEED_G5 [=y] && PINCTRL [=y] && (MACH_ASPEED_G5 [=n] ||
> COMPILE_TEST [=y]) && O>
>
> WARNING: unmet direct dependencies detected for PINCTRL_ASPEED
> Depends on [n]: PINCTRL [=y] && (ARCH_ASPEED [=n] || COMPILE_TEST
> [=y]) && OF [=y] && MFD_S>
> Selected by [y]:
> - PINCTRL_ASPEED_G6 [=y] && PINCTRL [=y] && (MACH_ASPEED_G6 [=n] ||
> COMPILE_TEST [=y]) && O>
>
> This is because PINCTRL_ASPEED_G* selects PINCTRL_ASPEED,
> without selecting or depending on MFD_SYSCON, despite
> PINCTRL_ASPEED depending on MFD_SYSCON.
>
> These unmet dependency bugs were detected by Kismet,
> a static analysis tool for Kconfig. Please advise
> if this is not the appropriate solution.
>
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
From a system-level perspective MFD_SYSCON is selected by ARCH_ASPEED,
then the MACH_ASPEED_G* symbols depend on ARCH_ASPEED.
However, that doesn't help the COMPILE_TEST case, so we need some
solution. Since MFD_SYSCON is required by all the relevant drivers and
the aspeed pinctrl core, maybe it would be best just to add as a select to
PINCTRL_ASPEED? Unless there's an argument for depends instead?
Thanks for the patch and report!
Andrew
> ---
> drivers/pinctrl/aspeed/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pinctrl/aspeed/Kconfig b/drivers/pinctrl/aspeed/Kconfig
> index de8b185c4fee..b0bae6144fc2 100644
> --- a/drivers/pinctrl/aspeed/Kconfig
> +++ b/drivers/pinctrl/aspeed/Kconfig
> @@ -11,6 +11,7 @@ config PINCTRL_ASPEED
> config PINCTRL_ASPEED_G4
> bool "Aspeed G4 SoC pin control"
> depends on (MACH_ASPEED_G4 || COMPILE_TEST) && OF
> + depends on MFD_SYSCON
> select PINCTRL_ASPEED
> help
> Say Y here to enable pin controller support for Aspeed's 4th
> @@ -19,6 +20,7 @@ config PINCTRL_ASPEED_G4
> config PINCTRL_ASPEED_G5
> bool "Aspeed G5 SoC pin control"
> depends on (MACH_ASPEED_G5 || COMPILE_TEST) && OF
> + depends on MFD_SYSCON
> select PINCTRL_ASPEED
> help
> Say Y here to enable pin controller support for Aspeed's 5th
> @@ -27,6 +29,7 @@ config PINCTRL_ASPEED_G5
> config PINCTRL_ASPEED_G6
> bool "Aspeed G6 SoC pin control"
> depends on (MACH_ASPEED_G6 || COMPILE_TEST) && OF
> + depends on MFD_SYSCON
> select PINCTRL_ASPEED
> help
> Say Y here to enable pin controller support for Aspeed's 6th
> --
> 2.30.2
prev parent reply other threads:[~2021-11-02 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 21:21 [PATCH] pinctrl: aspeed: fix unmet dependencies on MFD_SYSCON for PINCTRL_ASPEED Julian Braha
2021-11-02 22:46 ` Andrew Jeffery [this message]
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=3fc55e2b-05cb-438d-b1cb-0d62f26c5411@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=fazilyildiran@gmail.com \
--cc=joel@jms.id.au \
--cc=julianbraha@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).