From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Minda Chen <minda.chen@starfivetech.com>,
Roger Quadros <rogerq@kernel.org>
Cc: <linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: starfive: StarFive PHYs should depend on ARCH_STARFIVE
Date: Wed, 26 Jul 2023 09:30:59 +0800 [thread overview]
Message-ID: <cbc5b6e6-c706-b251-9a8e-0eecbc9871a8@starfivetech.com> (raw)
In-Reply-To: <12097f6107a18e2f7cfb80f47ac7b27808e062c4.1690300076.git.geert+renesas@glider.be>
On 2023/7/25 23:49, Geert Uytterhoeven wrote:
> The various StarFive PHYs are only present on StarFive SoCs. Hence add
> a dependency on ARCH_STARFIVE, to prevent asking the user about these
> drivers when configuring a kernel without StarFive SoC support.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/phy/starfive/Kconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/phy/starfive/Kconfig b/drivers/phy/starfive/Kconfig
> index a560533a674ee0a5..4457b3872aa146a4 100644
> --- a/drivers/phy/starfive/Kconfig
> +++ b/drivers/phy/starfive/Kconfig
> @@ -3,6 +3,8 @@
> # Phy drivers for StarFive platforms
> #
>
> +if ARCH_STARFIVE || COMPILE_TEST
> +
> config PHY_STARFIVE_JH7110_DPHY_RX
> tristate "StarFive JH7110 D-PHY RX support"
> select GENERIC_PHY
> @@ -31,3 +33,5 @@ config PHY_STARFIVE_JH7110_USB
> used with the Cadence USB controller.
> If M is selected, the module will be called
> phy-jh7110-usb.ko.
> +
> +endif # ARCH_STARFIVE || COMPILE_TEST
For dphy rx parts:
Acked-by: Changhuang Liang <changhuang.liang@starfivetech.com>
Thanks,
Changhuang
next prev parent reply other threads:[~2023-07-26 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 15:49 Geert Uytterhoeven
2023-07-26 1:30 ` Changhuang Liang [this message]
2023-07-26 13:39 ` Vinod Koul
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=cbc5b6e6-c706-b251-9a8e-0eecbc9871a8@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=geert+renesas@glider.be \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=minda.chen@starfivetech.com \
--cc=rogerq@kernel.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®