From: Simon Horman <horms@kernel.org>
To: Sky Huang <SkyLake.Huang@mediatek.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Daniel Golle <daniel@makrotopia.org>,
Qingfang Deng <dqfext@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Steven Liu <Steven.Liu@mediatek.com>
Subject: Re: [PATCH net-next v4 1/5] net: phy: mediatek: Re-organize MediaTek ethernet phy drivers
Date: Tue, 21 May 2024 17:36:39 +0100 [thread overview]
Message-ID: <20240521163639.GB839490@kernel.org> (raw)
In-Reply-To: <20240521101548.9286-2-SkyLake.Huang@mediatek.com>
On Tue, May 21, 2024 at 06:15:44PM +0800, Sky Huang wrote:
> From: "SkyLake.Huang" <skylake.huang@mediatek.com>
>
> Re-organize MediaTek ethernet phy driver files and get ready to integrate
> some common functions and add new 2.5G phy driver.
> mtk-ge.c: MT7530 Gphy on MT7621 & MT7531 Gphy
> mtk-ge-soc.c: Built-in Gphy on MT7981 & Built-in switch Gphy on MT7988
> mtk-2p5ge.c: Planned for built-in 2.5G phy on MT7988
>
> Signed-off-by: SkyLake.Huang <skylake.huang@mediatek.com>
...
> diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
> index 1df0595..e0e4b5e 100644
> --- a/drivers/net/phy/Kconfig
> +++ b/drivers/net/phy/Kconfig
> @@ -251,22 +251,7 @@ config MAXLINEAR_GPHY
> Support for the Maxlinear GPY115, GPY211, GPY212, GPY215,
> GPY241, GPY245 PHYs.
>
> -config MEDIATEK_GE_PHY
> - tristate "MediaTek Gigabit Ethernet PHYs"
> - help
> - Supports the MediaTek Gigabit Ethernet PHYs.
> -
> -config MEDIATEK_GE_SOC_PHY
> - tristate "MediaTek SoC Ethernet PHYs"
> - depends on (ARM64 && ARCH_MEDIATEK) || COMPILE_TEST
> - depends on NVMEM_MTK_EFUSE
> - help
> - Supports MediaTek SoC built-in Gigabit Ethernet PHYs.
> -
> - Include support for built-in Ethernet PHYs which are present in
> - the MT7981 and MT7988 SoCs. These PHYs need calibration data
> - present in the SoCs efuse and will dynamically calibrate VCM
> - (common-mode voltage) during startup.
> +source "drivers/net/phy/mediatek/Kconfig"
>
> config MICREL_PHY
> tristate "Micrel PHYs"
...
> diff --git a/drivers/net/phy/mediatek/Kconfig b/drivers/net/phy/mediatek/Kconfig
> new file mode 100644
> index 0000000..2fa3a78
> --- /dev/null
> +++ b/drivers/net/phy/mediatek/Kconfig
> @@ -0,0 +1,22 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +config MEDIATEK_GE_PHY
> + tristate "MediaTek Gigabit Ethernet PHYs"
> + help
> + Supports the MediaTek non-built-in Gigabit Ethernet PHYs.
> +
> + Non-built-in Gigabit Ethernet PHYs include mt7530/mt7531.
> + You may find mt7530 inside mt7621. This driver shares some
> + common operations with MediaTek SoC built-in Gigabit
> + Ethernet PHYs.
> +
> +config MEDIATEK_GE_SOC_PHY
> + bool "MediaTek SoC Ethernet PHYs"
Hi,
This patch changes this kconfig option from tristate to bool.
This seems to break allmodconfig builds.
I think that is because MEDIATEK_GE_SOC_PHY is builtin while
PHYLIB is a module, and this driver uses symbols from PHYLIB.
> + depends on (ARM64 && ARCH_MEDIATEK) || COMPILE_TEST
> + select NVMEM_MTK_EFUSE
> + help
> + Supports MediaTek SoC built-in Gigabit Ethernet PHYs.
> +
> + Include support for built-in Ethernet PHYs which are present in
> + the MT7981 and MT7988 SoCs. These PHYs need calibration data
> + present in the SoCs efuse and will dynamically calibrate VCM
> + (common-mode voltage) during startup.
...
--
pw-bot: changes-requested
next prev parent reply other threads:[~2024-05-21 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 10:15 [PATCH net-next v4 0/5] net: phy: mediatek: Introduce mtk-phy-lib and add 2.5Gphy support Sky Huang
2024-05-21 10:15 ` [PATCH net-next v4 1/5] net: phy: mediatek: Re-organize MediaTek ethernet phy drivers Sky Huang
2024-05-21 16:36 ` Simon Horman [this message]
2024-05-30 3:23 ` SkyLake Huang (黃啟澤)
2024-05-21 10:15 ` [PATCH net-next v4 2/5] net: phy: mediatek: Move LED and read/write page helper functions into mtk phy lib Sky Huang
2024-05-21 10:15 ` [PATCH net-next v4 3/5] net: phy: mediatek: Add token ring access helper functions in mtk-phy-lib Sky Huang
2024-05-21 10:15 ` [PATCH net-next v4 4/5] net: phy: mediatek: Extend 1G TX/RX link pulse time Sky Huang
2024-05-21 10:15 ` [PATCH net-next v4 5/5] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988 Sky Huang
2024-05-21 13:15 ` [PATCH net-next v4 0/5] net: phy: mediatek: Introduce mtk-phy-lib and add 2.5Gphy support Andrew Lunn
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=20240521163639.GB839490@kernel.org \
--to=horms@kernel.org \
--cc=SkyLake.Huang@mediatek.com \
--cc=Steven.Liu@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).