From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Kamil Horák (2N)" <kamilh@axis.com>,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
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,
f.fainelli@gmail.com, kory.maincent@bootlin.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 3/4] dt-bindings: ethernet-phy: add optional brr-mode flag
Date: Sun, 14 Jul 2024 13:12:35 -0700 [thread overview]
Message-ID: <a0be75e0-ee6d-4767-afa2-30c825db411c@broadcom.com> (raw)
In-Reply-To: <20240712150709.3134474-4-kamilh@axis.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On 7/12/2024 8:07 AM, Kamil Horák (2N) wrote:
> There is a group of PHY chips supporting BroadR-Reach link modes in
> a manner allowing for more or less identical register usage as standard
> Clause 22 PHY.
> These chips support standard Ethernet link modes as well, however, the
> circuitry is mutually exclusive and cannot be auto-detected.
> The link modes in question are 100Base-T1 as defined in IEEE802.3bw,
> based on Broadcom's 1BR-100 link mode, and newly defined 10Base-T1BRR
> (1BR-10 in Broadcom documents).
>
> Add optional brr-mode flag to switch the PHY to BroadR-Reach mode.
>
> Signed-off-by: Kamil Horák (2N) <kamilh@axis.com>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2024-07-14 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 15:07 [PATCH v12 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode Kamil Horák (2N)
2024-07-12 15:07 ` [PATCH v12 1/4] net: phy: bcm54811: New link mode for BroadR-Reach Kamil Horák (2N)
2024-07-12 15:07 ` [PATCH v12 2/4] net: phy: bcm54811: Add LRE registers definitions Kamil Horák (2N)
2024-07-13 18:21 ` Andrew Lunn
2024-07-14 20:12 ` Florian Fainelli
2024-07-12 15:07 ` [PATCH v12 3/4] dt-bindings: ethernet-phy: add optional brr-mode flag Kamil Horák (2N)
2024-07-14 20:12 ` Florian Fainelli [this message]
2024-07-12 15:07 ` [PATCH v12 4/4] net: phy: bcm-phy-lib: Implement BroadR-Reach link modes Kamil Horák (2N)
2024-07-13 18:30 ` Andrew Lunn
2024-07-14 20:13 ` Florian Fainelli
2024-07-15 4:40 ` [PATCH v12 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode patchwork-bot+netdevbpf
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=a0be75e0-ee6d-4767-afa2-30c825db411c@broadcom.com \
--to=florian.fainelli@broadcom.com \
--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=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kamilh@axis.com \
--cc=kory.maincent@bootlin.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 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).