From: Krzysztof Kozlowski <krzk@kernel.org>
To: Meghana Malladi <m-malladi@ti.com>, nm@ti.com, vigneshr@ti.com
Cc: kristo@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
andrew@lunn.ch, hkallweit1@gmail.com
Subject: Re: [RESEND PATCH] arm64: defconfig: Enable DP83TG720 PHY driver
Date: Fri, 27 Feb 2026 07:42:14 +0100 [thread overview]
Message-ID: <79e54fc3-9e61-44ff-9919-b1163bda81e5@kernel.org> (raw)
In-Reply-To: <20260226185448.2167189-1-m-malladi@ti.com>
On 26/02/2026 19:54, Meghana Malladi wrote:
> Enable DP83TG720 PHY driver as a module to support TI's DP83TG720
> 1000BASE-T1 Automotive Ethernet PHY. This is required for the
> DP83TG720-IND-SPE-EVM daughter card used with AM642 EVM ICSSG0
> interface.
Grepping for DP83TG720 or IND-SPE-EVM gives me no results. Are you sure
this is the board supported upstream?
>
> Signed-off-by: Meghana Malladi <m-malladi@ti.com>
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index b67d5b1fc45b..3b88df2ca5e1 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -420,6 +420,7 @@ CONFIG_REALTEK_PHY=y
> CONFIG_ROCKCHIP_PHY=y
> CONFIG_DP83867_PHY=y
> CONFIG_DP83869_PHY=m
> +CONFIG_DP83TG720_PHY=m
> CONFIG_DP83TD510_PHY=y
> CONFIG_VITESSE_PHY=y
> CONFIG_XILINX_GMII2RGMII=m
>
> base-commit: 4916f2e2f3fc9aef289fcd07949301e5c29094c2
> prerequisite-patch-id: d9e4c1f3ec36250ae7ce49b720614eef25f9ffd3
Why do you have dependencies in defconfig?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-27 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 18:54 [RESEND PATCH] arm64: defconfig: Enable DP83TG720 PHY driver Meghana Malladi
2026-02-27 6:42 ` Krzysztof Kozlowski [this message]
2026-02-27 7:15 ` Meghana Malladi
2026-02-27 7:21 ` Krzysztof Kozlowski
2026-02-27 7:24 ` Meghana Malladi
2026-02-27 7:29 ` Krzysztof Kozlowski
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=79e54fc3-9e61-44ff-9919-b1163bda81e5@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=vigneshr@ti.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