From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Gokul Praveen <g-praveen@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <conor+dt@kernel.org>,
<c-vankar@ti.com>, <krzk+dt@kernel.org>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <pabeni@redhat.com>, <kuba@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<s-vadapalli@ti.com>
Subject: Re: [PATCH v2 0/3] Add support for dual port USXGMII+SGMII
Date: Mon, 29 Jun 2026 16:50:52 +0530 [thread overview]
Message-ID: <ac7798b0-cf84-400d-b241-fd2f1088e7d7@ti.com> (raw)
In-Reply-To: <620d6a59-1e85-47c3-b7bd-2845f103f1d5@ti.com>
On 29/06/26 4:40 PM, Gokul Praveen wrote:
> Hi Siddharth,
>
> Thank your for the prompt feedback.
>
> On 29/06/26 16:16, Siddharth Vadapalli wrote:
>> On 29/06/26 15:53, Gokul Praveen wrote:
>>> This patch series enables dual port USXGMII and SGMII Ethernet mode
>>> support on the TI J784S4 EVM platform using the CPSW9G Ethernet switch.
>>
>> Patch 1 => For Bindings
>> Patch 2 => For Driver
>> Patch 3 => For Device-tree overlay
>>
>> Please split patch 1 and patch 2 into a different patch series and
>> post patch 3 only after patches 1 and 2 are merged. Also, the patch
>> series containing patches 1 and 2 should have the 'net-next' suffix in
>> the patch subject:
>> [PATCH net-next ...]
>
> Sure, I will add the 'net-next' suffix ,siddharth.
>
>>
>> Additionally, the subject for Patch 1 looks incorrect as it doesn't
>> follow the format expected for Bindings patches.
>>
> Sure, I will follow the format.
>>>
>>> The CPSW9G instance supports both SGMII and USXGMII modes simultaneously
>>> on MAC Ports 1 and 2, which connect to ENET Expansion 1 and ENET
>>> Expansion 2 slots through the SERDES2 instance. The series includes:
>>>
>>> 1. A fix to the SERDES2 node to add the missing PLL1 refclk, which is
>>> required for multilink SERDES configuration to function properly.
>>
>> Is it a 'fix' or a 'feature'? Please don't use them interchangeably.
>> If it is a 'fix', which commit is it fixing? Specifically, which
>> commit 'claimed' to enable the configuration that you seem to be fixing?
> Yes, it is a feature, siddharth. I will change the commit description.
>>
>>>
>>> 2. A driver fix for the am65-cpsw Ethernet driver to properly configure
>>> the MAC in SGMII mode according to the CPSGMII Module specification,
>>> including correct advertisement ability register settings and master
>>> mode configuration.
>>
>> Although you have called it a 'fix' again, the CPSW is a MAC and not
>> an Ethernet PHY. Therefore, the existing configuration is intended to
>> advertise CPSW as an SGMII capable MAC (SGMII Slave Mode Configuration).
>>
>> For more details, please refer:
>> https://lore.kernel.org/all/20220914095053.189851-6-s-vadapalli@ti.com/
>>
>> [TRIMMED]
>
>
> Actually, this patch which you have mentioned "https://lore.kernel.org/
> all/20220914095053.189851-6-s-vadapalli@ti.com/" is no longer present in
> the latest kernel driver , siddharth.
That was exactly my point. Please go through the conversation on my
patch to understand why the patch isn't correct.
Regards,
Siddharth.
prev parent reply other threads:[~2026-06-29 11:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 10:23 [PATCH v2 0/3] Add support for dual port USXGMII+SGMII Gokul Praveen
2026-06-29 10:23 ` [PATCH v2 1/3] arm64: dts: ti: Add PLL1 refclk to J784S4 SoC SERDES node Gokul Praveen
2026-06-29 10:31 ` sashiko-bot
2026-06-29 10:47 ` Gokul Praveen
2026-06-30 7:13 ` Krzysztof Kozlowski
2026-06-30 12:59 ` Gokul Praveen
2026-06-29 10:23 ` [PATCH v2 2/3] net: ethernet: ti: am65-cpsw: Fix MAC configuration for SGMII mode Gokul Praveen
2026-06-29 12:37 ` sashiko-bot
2026-06-29 22:12 ` Jakub Kicinski
2026-06-30 12:55 ` Gokul Praveen
2026-06-29 10:23 ` [PATCH v2 3/3] arm64: dts: ti: k3-j784s4: Add overlay for dual port USXGMII+SGMII mode Gokul Praveen
2026-06-29 10:34 ` sashiko-bot
2026-06-29 10:58 ` Gokul Praveen
2026-06-29 10:46 ` [PATCH v2 0/3] Add support for dual port USXGMII+SGMII Siddharth Vadapalli
2026-06-29 11:10 ` Gokul Praveen
2026-06-29 11:20 ` Siddharth Vadapalli [this message]
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=ac7798b0-cf84-400d-b241-fd2f1088e7d7@ti.com \
--to=s-vadapalli@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=g-praveen@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pabeni@redhat.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