From: Andrew Lunn <andrew@lunn.ch>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: 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>,
Catalin Popescu <catalin.popescu@leica-geosystems.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] net: phy: dp83826: Add support for straps reading
Date: Mon, 3 Mar 2025 18:50:48 +0100 [thread overview]
Message-ID: <bf0228a7-032d-4d8c-b5e1-1be4830404f7@lunn.ch> (raw)
In-Reply-To: <7cd18e37-2d68-4825-bcc4-fc2ac6b9a461@yoseli.org>
On Mon, Mar 03, 2025 at 06:37:28PM +0100, Jean-Michel Hautbois wrote:
> Hi Andrew,
>
> On 03/03/2025 18:20, Andrew Lunn wrote:
> > On Mon, Mar 03, 2025 at 06:05:52PM +0100, Jean-Michel Hautbois wrote:
> > > When the DP83826 is probed, read the straps, and apply the default
> > > settings expected. The MDI-X is not yet supported, but still read the
> > > strap.
> >
> > What about backwards compatibility? I expect this changes the
> > behaviour of the device, potentially introducing regressions? Please
> > add an explanation of why this is safe.
>
> I am not certain it is safe. As far as I know that if straps are used on the
> hardware, then it should be used, and if the behavior has to be different,
> then userspace can change it (or any other way). Am I wrong ?
First off, what does the datasheet say about these straps?
Straps generally configure the hardware, without software being
involved. It seems odd you need software to read the straps and apply
them.
Why do you need this? What is your use case. As you said, user space
can configure all this, so why are you not doing that?
Andrew
next prev parent reply other threads:[~2025-03-03 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 17:05 [PATCH 0/2] net: phy: dp83826: Enable strap reading and fix TX data voltage support Jean-Michel Hautbois
2025-03-03 17:05 ` [PATCH 1/2] net: phy: dp83826: Fix " Jean-Michel Hautbois
2025-03-14 9:00 ` Jean-Michel Hautbois
2025-03-03 17:05 ` [PATCH 2/2] net: phy: dp83826: Add support for straps reading Jean-Michel Hautbois
2025-03-03 17:20 ` Andrew Lunn
2025-03-03 17:37 ` Jean-Michel Hautbois
2025-03-03 17:50 ` Andrew Lunn [this message]
2025-03-03 17:53 ` Jean-Michel Hautbois
2025-03-04 6:37 ` Jean-Michel Hautbois
2025-03-03 17:25 ` Russell King (Oracle)
2025-03-03 17:35 ` Jean-Michel Hautbois
2025-03-03 18:08 ` Russell King (Oracle)
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=bf0228a7-032d-4d8c-b5e1-1be4830404f7@lunn.ch \
--to=andrew@lunn.ch \
--cc=catalin.popescu@leica-geosystems.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®