From: Conor Dooley <conor@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Kamil Horák (2N)" <kamilh@axis.com>,
florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 3/4] dt-bindings: ethernet-phy: add optional brr-mode flag
Date: Fri, 5 Jul 2024 15:51:06 +0100 [thread overview]
Message-ID: <20240705-curing-lisp-c10eccf74685@spud> (raw)
In-Reply-To: <35d571bd-251d-45b5-9e4f-93c83d1a43c8@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Thu, Jul 04, 2024 at 11:11:41PM +0200, Andrew Lunn wrote:
> > > ---
> > > Documentation/devicetree/bindings/net/ethernet-phy.yaml | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> > > index 8fb2a6ee7e5b..349ae72ebf42 100644
> > > --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> > > +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> > > @@ -93,6 +93,14 @@ properties:
> > > the turn around line low at end of the control phase of the
> > > MDIO transaction.
> > >
> > > + brr-mode:
> > > + $ref: /schemas/types.yaml#/definitions/flag
> > > + description:
> > > + If set, indicates the network cable interface is alternative one as
nit: an alternative
> > > + defined in the BroadR-Reach link mode specification under 1BR-100 and
> > > + 1BR-10 names. The driver needs to configure the PHY to operate in
> > > + BroadR-Reach mode.
> >
> > I find this second sentence unclear. Does the driver need to do
> > configure the phy because this mode is not enabled by default or because
> > the device will not work outside of this mode.
>
> BroadR-Reach uses one pair. Standard 10/100Mbps ethernet needs 2 pair,
> and 1G needs 4 pair. So any attempt to use standard 10/100/1G is going
> to fail, the socket/plug and cable just don't work for anything other
> than BroadR-Reach.
>
> As far as i understand it, the PHY could be strapped into BroadR-Reach
> mode, but there is no guarantee it is, so we should also program it to
> BroadR-Reach mode if this property is present.
Right, I guess for people that want brr-mode they'll probably understand
that and it's just unclear to me as I don't :) The nitpicking side of my
brain would like that last sentence reworded to "The PHY must be
configured to operate in BroadR-Reach mode by software", mostly cos the
word "driver" assumes a particular model for the OS, but it's not really
a big deal.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-05 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 14:04 [PATCH v10 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode Kamil Horák (2N)
2024-07-04 14:04 ` [PATCH v10 1/4] net: phy: bcm54811: New link mode for BroadR-Reach Kamil Horák (2N)
2024-07-04 14:04 ` [PATCH v10 2/4] net: phy: bcm54811: Add LRE registers definitions Kamil Horák (2N)
2024-07-04 14:04 ` [PATCH v10 3/4] dt-bindings: ethernet-phy: add optional brr-mode flag Kamil Horák (2N)
2024-07-04 16:17 ` Conor Dooley
2024-07-04 21:11 ` Andrew Lunn
2024-07-05 14:51 ` Conor Dooley [this message]
2024-07-04 14:04 ` [PATCH v10 4/4] net: phy: bcm-phy-lib: Implement BroadR-Reach link modes Kamil Horák (2N)
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=20240705-curing-lisp-c10eccf74685@spud \
--to=conor@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=kamilh@axis.com \
--cc=krzk+dt@kernel.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 \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.