From: Meghana Malladi <m-malladi@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <nm@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>,
"Raghavendra, Vignesh" <vigneshr@ti.com>
Subject: Re: [RESEND PATCH] arm64: defconfig: Enable DP83TG720 PHY driver
Date: Fri, 27 Feb 2026 12:54:28 +0530 [thread overview]
Message-ID: <1cc7fb44-c08c-4f62-ba88-20434b4954aa@ti.com> (raw)
In-Reply-To: <76067a68-62b2-4e45-9bf4-6765be61b7f7@kernel.org>
On 2/27/26 12:51, Krzysztof Kozlowski wrote:
> On 27/02/2026 08:15, Meghana Malladi wrote:
>>
>>
>> On 2/27/26 12:12, Krzysztof Kozlowski wrote:
>>> 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?
>>>
>>
>> Yes, this series adds support adds support for the board:
>> https://lore.kernel.org/all/20231212054144.87527-1-o.rempel@pengutronix.de/
>
> I still wonder why there is no DTS for this.
>
I posted DTS patch separately for this:
https://lore.kernel.org/all/20260226115454.1730618-1-m-malladi@ti.com/
Does it make more sense to post them together as a series ?
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-02-27 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 18:54 Meghana Malladi
2026-02-27 6:42 ` Krzysztof Kozlowski
2026-02-27 7:15 ` Meghana Malladi
2026-02-27 7:21 ` Krzysztof Kozlowski
2026-02-27 7:24 ` Meghana Malladi [this message]
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=1cc7fb44-c08c-4f62-ba88-20434b4954aa@ti.com \
--to=m-malladi@ti.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kristo@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®