From: Ziyang Huang <hzyitc@outlook.com>
To: andrew@lunn.ch
Cc: olteanv@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,
rmk+kernel@armlinux.org.uk, javier.carrasco.cruz@gmail.com,
hzyitc@outlook.com, john@phrozen.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] net: dsa: qca8k: support internal-PHY-to-PHY CPU link
Date: Mon, 3 Mar 2025 23:22:40 +0800 [thread overview]
Message-ID: <TYZPR01MB555632DC209AA69996309B58C9C92@TYZPR01MB5556.apcprd01.prod.exchangelabs.com> (raw)
internal-PHY-to-PHY CPU link is a common/demo design in IPQ50xx platform,
since it only has a SGMII/SGMII+ link and a MDI link.
For DSA, CPU tag is the only requirement. Fortunately, qca8337 can enable
it on any port. So it's ok to trust a internal-PHY-to-PHY link as a CPU
link.
Ziyang Huang (2):
net: dsa: qca8k: support internal-PHY-to-PHY CPU link
dt-bindings: net: dsa: qca8k: add internal-PHY-to-PHY CPU link example
Documentation/devicetree/bindings/net/dsa/qca8k.yaml | 7 +++++--
drivers/net/dsa/qca/qca8k-8xxx.c | 12 +++++++-----
2 files changed, 12 insertions(+), 7 deletions(-)
--
2.40.1
next reply other threads:[~2025-03-03 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 15:22 Ziyang Huang [this message]
2025-03-03 15:24 ` [PATCH 1/2] " Ziyang Huang
2025-03-03 15:24 ` [PATCH 2/2] dt-bindings: net: dsa: qca8k: add internal-PHY-to-PHY CPU link example Ziyang Huang
2025-03-03 16:15 ` Andrew Lunn
2025-03-03 16:37 ` Ziyang Huang
2025-03-03 17:15 ` Andrew Lunn
2025-03-04 5:00 ` Ziyang Huang
[not found] ` <dbd0e376-d7c3-4ba9-886b-ba9529a2ec4e@outlook.com>
2025-03-04 14:11 ` Andrew Lunn
2025-03-05 14:41 ` Ziyang Huang
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=TYZPR01MB555632DC209AA69996309B58C9C92@TYZPR01MB5556.apcprd01.prod.exchangelabs.com \
--to=hzyitc@outlook.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=john@phrozen.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®