From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "Richard Zhu" <hongxing.zhu@nxp.com>, "Li Jun" <jun.li@nxp.com>,
"Guido Günther" <agx@sigxcpu.org>,
"Kishon Vijay Abraham I" <kishon@ti.com>
Cc: Vinod Koul <vkoul@kernel.org>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH] phy: freescale: i.MX8 PHYs should depend on ARCH_MXC && ARM64
Date: Wed, 12 Jan 2022 12:40:38 +0100 [thread overview]
Message-ID: <393868affd830016d35f0d9aba32ccd7098c8073.1641987369.git.geert+renesas@glider.be> (raw)
The Freescale/NXP i.MX8 USB3, MIPI DSI, and PCIE PHYs are only present
on the NXP i.MX8 family of SoCs. Hence wrap the config symbols for
these PHYs inside a check for ARCH_MXC && ARM64, to prevent asking the
user about these drivers when configuring a kernel without NXP i.MX SoC
family support.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/phy/freescale/Kconfig | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/phy/freescale/Kconfig b/drivers/phy/freescale/Kconfig
index c3669c28ea9fe83a..856cbec7057d9e54 100644
--- a/drivers/phy/freescale/Kconfig
+++ b/drivers/phy/freescale/Kconfig
@@ -1,4 +1,7 @@
# SPDX-License-Identifier: GPL-2.0-only
+
+if (ARCH_MXC && ARM64) || COMPILE_TEST
+
config PHY_FSL_IMX8MQ_USB
tristate "Freescale i.MX8M USB3 PHY"
depends on OF && HAS_IOMEM
@@ -22,3 +25,5 @@ config PHY_FSL_IMX8M_PCIE
help
Enable this to add support for the PCIE PHY as found on
i.MX8M family of SOCs.
+
+endif
--
2.25.1
next reply other threads:[~2022-01-12 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:40 Geert Uytterhoeven [this message]
2022-01-12 14:20 ` [PATCH] phy: freescale: i.MX8 PHYs should depend on ARCH_MXC && ARM64 Guido Günther
2022-01-27 5:35 ` 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=393868affd830016d35f0d9aba32ccd7098c8073.1641987369.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=agx@sigxcpu.org \
--cc=hongxing.zhu@nxp.com \
--cc=jun.li@nxp.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).