From: "Frank.Sae" <Frank.Sae@motor-comm.com>
To: Frank.Sae@motor-comm.com, andrew@lunn.ch, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux@armlinux.org.uk
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, yuanlai.cui@motor-comm.com,
hua.sun@motor-comm.com, xiaoyong.li@motor-comm.com,
suting.hu@motor-comm.com, jie.han@motor-comm.com
Subject: [PATCH 1/2] dt-bindings: net: motorcomm: Add chip mode cfg
Date: Sat, 27 Jul 2024 02:20:09 -0700 [thread overview]
Message-ID: <20240727092009.1108640-1-Frank.Sae@motor-comm.com> (raw)
The motorcomm phy (yt8821) supports the ability to
config the chip mode of serdes.
The yt8821 serdes could be set to AUTO_BX2500_SGMII or
FORCE_BX2500.
In AUTO_BX2500_SGMII mode, SerDes
speed is determined by UTP, if UTP link up
at 2.5GBASE-T, SerDes will work as
2500BASE-X, if UTP link up at
1000BASE-T/100BASE-Tx/10BASE-T, SerDes will work
as SGMII.
In FORCE_BX2500, SerDes always works
as 2500BASE-X.
Signed-off-by: Frank.Sae <Frank.Sae@motor-comm.com>
---
.../bindings/net/motorcomm,yt8xxx.yaml | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml b/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
index 26688e2302ea..ba34260f889d 100644
--- a/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
+++ b/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
@@ -110,6 +110,23 @@ properties:
Transmit PHY Clock delay train configuration when speed is 1000Mbps.
type: boolean
+ motorcomm,chip-mode:
+ description: |
+ Only for yt8821 2.5G phy, it supports two chip working modes,
+ one is AUTO_BX2500_SGMII, the other is FORCE_BX2500.
+ If this property is not set in device tree node then driver
+ selects chip mode FORCE_BX2500 by default.
+ 0: AUTO_BX2500_SGMII
+ 1: FORCE_BX2500
+ In AUTO_BX2500_SGMII mode, serdes speed is determined by UTP,
+ if UTP link up at 2.5GBASE-T, serdes will work as 2500BASE-X,
+ if UTP link up at 1000BASE-T/100BASE-Tx/10BASE-T, serdes will
+ work as SGMII.
+ In FORCE_BX2500 mode, serdes always works as 2500BASE-X.
+ $ref: /schemas/types.yaml#/definitions/uint8
+ enum: [ 0, 1 ]
+ default: 1
+
unevaluatedProperties: false
examples:
--
2.25.1
next reply other threads:[~2024-07-27 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 9:20 Frank.Sae [this message]
2024-07-27 9:25 ` [PATCH 1/2] dt-bindings: net: motorcomm: Add chip mode cfg Krzysztof Kozlowski
2024-07-27 11:07 ` Andrew Lunn
2024-08-11 12:45 ` Frank.Sae
[not found] ` <f18fa949-b217-4373-82c4-7981872446b4@motor-comm.com>
2024-08-01 13:14 ` Andrew Lunn
2024-08-11 13:09 ` Frank.Sae
2024-08-01 14:23 ` Krzysztof Kozlowski
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=20240727092009.1108640-1-Frank.Sae@motor-comm.com \
--to=frank.sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=hua.sun@motor-comm.com \
--cc=jie.han@motor-comm.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 \
--cc=suting.hu@motor-comm.com \
--cc=xiaoyong.li@motor-comm.com \
--cc=yuanlai.cui@motor-comm.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