From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Suraj Gupta <suraj.gupta2@amd.com>,
radhey.shyam.pandey@amd.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, michal.simek@amd.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, git@amd.com,
harini.katakam@amd.com
Subject: Re: [PATCH net-next V2 2/2] net: axienet: Add support for 2500base-X only configuration.
Date: Wed, 12 Mar 2025 14:13:54 +0000 [thread overview]
Message-ID: <Z9GWokRDzEYwJmBz@shell.armlinux.org.uk> (raw)
In-Reply-To: <ad1e81b5-1596-4d94-a0fa-1828d667b7a2@lunn.ch>
On Wed, Mar 12, 2025 at 02:25:27PM +0100, Andrew Lunn wrote:
> > + /* AXI 1G/2.5G ethernet IP has following synthesis options:
> > + * 1) SGMII/1000base-X only.
> > + * 2) 2500base-X only.
> > + * 3) Dynamically switching between (1) and (2), and is not
> > + * implemented in driver.
> > + */
> > +
> > + if (axienet_ior(lp, XAE_ABILITY_OFFSET) & XAE_ABILITY_2_5G)
>
> How can we tell if the synthesis allows 3)?
>
> Don't we have a backwards compatibility issue here? Maybe there are
> systems which have been synthesised with 3), but are currently limited
> to 1) due to the driver. If you don't differentiate between 2 and 3,
> such systems are going to swap to 2) and regress.
We've discussed this before... but because the author doesn't post
regularly enough, it's not suprising that context keeps getting lost.
Here's the discussion from 20th February 2025 on a patch series that I
commented on on 19th November 2024.
https://lore.kernel.org/r/BL3PR12MB6571FE73FA8D5AAB9FB4BB3CC9C42@BL3PR12MB6571.namprd12.prod.outlook.com
Suraj Gupta - you _must_ be more responsive so that reviewers can keep
the context of previous discussions in their heads to avoid going over
the same points time and time again. If you can't do that (and it's a
good idea anyway) then you need to supplement the commit descriptions
with the salient points from the previous patch series discussion to
remind reviewers of the appropriate context.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-03-12 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:54 [PATCH net-next V2 0/2] Add support for 2500Base-X only configuration Suraj Gupta
2025-03-12 9:54 ` [PATCH net-next V2 1/2] dt-bindings: net: xlnx,axi-ethernet: Modify descriptions and phy-mode value to support 2500base-X " Suraj Gupta
2025-03-12 13:17 ` Rob Herring
2025-03-12 9:54 ` [PATCH net-next V2 2/2] net: axienet: Add support for " Suraj Gupta
2025-03-12 11:06 ` Dawid Osuchowski
2025-03-12 13:25 ` Andrew Lunn
2025-03-12 14:13 ` Russell King (Oracle) [this message]
2025-03-12 14:49 ` Gupta, Suraj
2025-03-12 14:58 ` Andrew Lunn
2025-03-12 15:06 ` Gupta, Suraj
2025-03-12 15:33 ` Andrew Lunn
2025-03-12 16:08 ` Gupta, Suraj
2025-03-12 19:02 ` Andrew Lunn
2025-03-12 19:40 ` Russell King (Oracle)
2025-03-12 22:10 ` Andrew Lunn
2025-03-13 3:31 ` Gupta, Suraj
2025-03-13 7:34 ` Gupta, Suraj
2025-03-13 12:47 ` Andrew Lunn
2025-03-19 18:41 ` Gupta, Suraj
2025-03-13 12:54 ` 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=Z9GWokRDzEYwJmBz@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh@kernel.org \
--cc=suraj.gupta2@amd.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).