From: Kyle Switch <kyle.switch@motor-comm.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Yang <mmyangfl@gmail.com>,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.xu@motor-comm.com,
xiaolin.xu@motor-comm.com, jianmin.wang@motor-comm.com,
wei.zhang@gl-inet.com, sijia.huang@gl-inet.com
Subject: Re: [PATCH net-next v6 6/6] net: dsa: motorcomm: Add support for Motorcomm YT922x
Date: Thu, 10 Sep 2026 11:23:03 +0800 [thread overview]
Message-ID: <1bd79ceb-4abf-49e3-a441-7c026a89d220@motor-comm.com> (raw)
In-Reply-To: <0ad7cd3b-006f-41a0-9d58-5f6dad9c22e8@lunn.ch>
On 9/10/26 09:57, Andrew Lunn wrote:
>>>> No one else, except you, can maintain this stuff. Drop it for now and
>>>> discuss it later.
>>> There also appears to be similar magic in the PHY driver. Can this be
>>> consolidated?
>> Ans: This part of the initialization is for the switch SerDes, so from my
>>
>> side it may be hard to consolidate.
> Is it the same IP? Same configuration? Or totally different?
Ans: They are the same IP, but there are the following differences:
1. phy8824 only supports usxgmii_multiport mode.
yt922x has 4utp+2serdes. These two serdes support more modes,
such as usxgmii_singleport, bx1000, sgmii, etc., which results in more
initialization configurations for the switch serdes.
2. Another point that I think is difficult to integrate is that the phyID
of the switch serdes (defined in USXGMII reg space mii 0x2, 0x3) is
inconsistent with the phyID of phy8824 (defined in UTP reg space
mii 0x2, 0x3),
so phy8824 cannot be matched, and therefore two sets of initialization
configurations are required.
> Andrew
next prev parent reply other threads:[~2026-09-10 3:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 8:36 [PATCH net-next v6 0/6] net: dsa: motorcomm: add support yt922x driver Kyle Switch
2026-09-08 8:36 ` [PATCH net-next v6 1/6] net: dsa: motorcomm: initialize dsa_switch based on chipid Kyle Switch
2026-09-09 16:18 ` David Yang
2026-09-10 2:13 ` Kyle Switch
2026-09-08 8:36 ` [PATCH net-next v6 2/6] net: dsa: motorcomm: use max_ports in series for port bounds checking Kyle Switch
2026-09-08 8:36 ` [PATCH net-next v6 3/6] net: dsa: motorcomm: move mib start from probe() to dsa_setup() Kyle Switch
2026-09-08 8:36 ` [PATCH net-next v6 4/6] net: dsa: motorcomm: move mib stop from remove() to teardown() Kyle Switch
2026-09-08 8:36 ` [PATCH net-next v6 5/6] net: dsa: tag_yt922x: add support for Motorcomm YT922x tags Kyle Switch
2026-09-08 8:36 ` [PATCH net-next v6 6/6] net: dsa: motorcomm: Add support for Motorcomm YT922x Kyle Switch
2026-09-09 16:51 ` David Yang
2026-09-09 17:32 ` Andrew Lunn
2026-09-10 1:50 ` Kyle Switch
2026-09-10 1:57 ` Andrew Lunn
2026-09-10 3:23 ` Kyle Switch [this message]
2026-09-10 11:58 ` Andrew Lunn
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=1bd79ceb-4abf-49e3-a441-7c026a89d220@motor-comm.com \
--to=kyle.switch@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jianmin.wang@motor-comm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ming.xu@motor-comm.com \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sijia.huang@gl-inet.com \
--cc=wei.zhang@gl-inet.com \
--cc=xiaolin.xu@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