From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Justin Lai <justinlai0215@realtek.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pkshih@realtek.com, larry.chiu@realtek.com
Subject: Re: [PATCH net-next v13 01/13] rtase: Add pci table supported in this module
Date: Sat, 2 Dec 2023 10:58:45 -0800 [thread overview]
Message-ID: <20231202105845.12e27e31@kernel.org> (raw)
In-Reply-To: <27b2b87a-929d-4b97-9265-303391982d27@lunn.ch>
On Sat, 2 Dec 2023 17:27:57 +0100 Andrew Lunn wrote:
> > > + * The block of the Realtek RTL90xx series is our entire chip architecture,
> > > + * the GMAC is connected to the switch core, and there is no PHY in between.
> > > + * In addition, this driver is mainly used to control GMAC, but does not
> > > + * control the switch core, so it is not the same as DSA.
> >
> > Okay, but you seem to only register one netdev.
> >
> > Which MAC is it for?
>
> The GMAC one. This is going to be a DSA system, and this driver is for
> the conduit MAC the CPU uses. At some point, i hope there is a DSA
> driver added, or the existing realtek driver is extended to support
> this switch.
Oh, thanks, it even says so in the comment. I blame it on late night
reviewing. I was confused by the "driver [...] does not control the
switch core, so it is not the same as DSA." Looking at the discussion
in v3 it sounds like the switch is controlled by a different PCI
function? In which case it very much sounds like DSA. Or maybe there
was a minor misunderstanding there, and the driver will need MFD /
auxbus, which is still close to DSA.
I'm mainly asking to make sure we avoid "implicitly programming" the
switch, like, IIUC, one of the TI drivers did. And we ended up with
multiple versions / modes of operation :( Sounds like this driver
doesn't touch switch registers yet, tho, so all good.
next prev parent reply other threads:[~2023-12-02 18:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 11:43 [PATCH net-next v13 00/13] Add Realtek automotive PCIe driver Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 01/13] rtase: Add pci table supported in this module Justin Lai
2023-12-02 4:36 ` Jakub Kicinski
2023-12-02 16:27 ` Andrew Lunn
2023-12-02 18:58 ` Jakub Kicinski [this message]
2023-12-02 19:09 ` Andrew Lunn
2023-12-06 3:28 ` Justin Lai
2023-12-06 3:40 ` Jakub Kicinski
2023-12-08 9:27 ` Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 02/13] rtase: Implement the .ndo_open function Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 03/13] rtase: Implement the rtase_down function Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 04/13] rtase: Implement the interrupt routine and rtase_poll Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 05/13] rtase: Implement hardware configuration function Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 06/13] rtase: Implement .ndo_start_xmit function Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 07/13] rtase: Implement a function to receive packets Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 08/13] rtase: Implement net_device_ops Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 09/13] rtase: Implement pci_driver suspend and resume function Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 10/13] rtase: Implement ethtool function Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 11/13] rtase: Add a Makefile in the rtase folder Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 12/13] realtek: Update the Makefile and Kconfig in the realtek folder Justin Lai
2023-11-30 11:43 ` [PATCH net-next v13 13/13] MAINTAINERS: Add the rtase ethernet driver entry Justin Lai
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=20231202105845.12e27e31@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=justinlai0215@realtek.com \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).