netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
	f.fainelli@gmail.com, olteanv@gmail.com, netdev@vger.kernel.org,
	chris.packham@alliedtelesis.co.nz, pabeni@redhat.com,
	marek.behun@nic.cz
Subject: Re: [PATCH v2 net 3/4] net: dsa: mv88e6xxx: Never force link on in-band managed MACs
Date: Mon, 6 Jan 2025 08:20:44 +0000	[thread overview]
Message-ID: <Z3uSXFH9bryiuVqX@shell.armlinux.org.uk> (raw)
In-Reply-To: <87h66c7sa6.fsf@waldekranz.com>

On Mon, Jan 06, 2025 at 12:30:25AM +0100, Tobias Waldekranz wrote:
> On sön, jan 05, 2025 at 10:41, "Russell King (Oracle)" <linux@armlinux.org.uk> wrote:
> > On Sun, Jan 05, 2025 at 12:16:07AM +0100, Tobias Waldekranz wrote:
> >> On lör, jan 04, 2025 at 22:09, "Russell King (Oracle)" <linux@armlinux.org.uk> wrote:
> >> > Host system:
> >> >
> >> >   ---------------------------+
> >> >     NIC (or DSA switch port) |
> >> >      +-------+    +-------+  |
> >> >      |       |    |       |  |
> >> >      |  MAC  <---->  PCS  <-----------------------> PHY, SFP or media
> >> >      |       |    |       |  |     ^
> >> >      +-------+    +-------+  |     |
> >> >                              |   phy interface type
> >> >   ---------------------------+   also in-band signalling
> >> >                                  which managed = "in-band-status"
> >> > 				 applies to
> >> 
> >> This part is 100% clear
> >
> > Apparently it isn't, because...
> >
> >> In other words, my question is:
> >> 
> >> For a NIC driver to properly support the `managed` property, how should
> >> the setup and/or runtime behavior of the hardware and/or the driver
> >> differ with the two following configs?
> >> 
> >>     &eth0 {
> >>         phy-connection-type = "sgmii";
> >>         managed = "auto";
> >>     };
> >> 
> >> vs.
> >> 
> >>     &eth0 {
> >>         phy-connection-type = "sgmii";
> >>         managed = "in-band-status";
> >>     };
> >
> > if it were, you wouldn't be asking this question.
> >
> > Once again. The "managed" property defines whether in-band signalling
> > is used over the "phy-connection-type" link, which for SGMII will be
> > between the PCS and PHY, as shown in my diagram above that you claim
> > to understand 100%, but by the fact you are again asking this question,
> > you do not understand it AT ALL.
> >
> > I don't know how to better explain it to you, because I think I've been
> > absolutely clear at every stage what the "managed" property describes.
> > I now have nothing further to add if you still can't understand it, so,
> > sorry, I'm giving up answering your emails on this topic, because it's
> > just too frustrating to me to continue if you still don't "get it".
> 
> I agree that you have clearly explained what it describes, many times.
> 
> My remaining question - which you acknowledge that I asked twice, yet
> chose not to answer - was how software is supposed to _act_ on that

I *have* answered it. Every time.

> description; presuming that the property is not in the DT merely for
> documentation purposes.

Utter claptap. Total rubbish. Completely wrong. It is acted on. It
causes phylink to enter in-band mode, and use the PCS to obtain the
in-band data instead of the PHY.

YOU are the one refusing to listen to what I'm saying, yet you claim
my explanations are clear and you understand them. You parently do
not.

End. Of. Discussion.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2025-01-06  8:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 12:30 [PATCH v2 net 0/4] net: dsa: mv88e6xxx: Amethyst (6393X) fixes Tobias Waldekranz
2024-12-19 12:30 ` [PATCH v2 net 1/4] net: dsa: mv88e6xxx: Improve I/O related error logging Tobias Waldekranz
2024-12-19 13:41   ` Andrew Lunn
2024-12-19 14:32   ` Vladimir Oltean
2024-12-19 12:30 ` [PATCH v2 net 2/4] net: dsa: mv88e6xxx: Give chips more time to activate their PPUs Tobias Waldekranz
2024-12-19 13:41   ` Andrew Lunn
2024-12-19 12:30 ` [PATCH v2 net 3/4] net: dsa: mv88e6xxx: Never force link on in-band managed MACs Tobias Waldekranz
2024-12-19 13:43   ` Andrew Lunn
2025-01-02 10:31   ` Russell King (Oracle)
2025-01-02 13:06     ` Tobias Waldekranz
2025-01-02 17:08       ` Russell King (Oracle)
2025-01-04 21:37         ` Tobias Waldekranz
2025-01-04 22:09           ` Russell King (Oracle)
2025-01-04 23:16             ` Tobias Waldekranz
2025-01-05 10:41               ` Russell King (Oracle)
2025-01-05 23:30                 ` Tobias Waldekranz
2025-01-06  8:20                   ` Russell King (Oracle) [this message]
2025-01-06 14:39                     ` Tobias Waldekranz
2024-12-19 12:30 ` [PATCH v2 net 4/4] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user ports on 6393X Tobias Waldekranz
2024-12-19 13:44   ` Andrew Lunn
2024-12-19 14:05   ` Vladimir Oltean
2024-12-19 14:14     ` Vladimir Oltean
2024-12-19 14:34     ` Tobias Waldekranz
2024-12-19 14:42       ` Vladimir Oltean
2024-12-19 14:52         ` Vladimir Oltean
2024-12-19 15:02           ` Tobias Waldekranz
2024-12-19 14:29   ` Vladimir Oltean

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=Z3uSXFH9bryiuVqX@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=marek.behun@nic.cz \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=tobias@waldekranz.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).