mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next v2] net: pcs: airoha: add support for Airoha AN7583 SoC
Date: Fri, 25 Sep 2026 14:18:34 +0200	[thread overview]
Message-ID: <6ab6669c.232cdbff.15fa39.f0d3@mx.google.com> (raw)
In-Reply-To: <12d6e310-3aa9-45f1-925e-e3c8f2f0efad@lunn.ch>

On Fri, Sep 25, 2026 at 02:07:52PM +0200, Andrew Lunn wrote:
> > +static void an7583_pcs_setup_scu_pcie(struct airoha_pcs_priv *priv,
> > +				      int index, phy_interface_t interface)
> > +{
> > +	u32 xsi_sel;
> > +
> > +	if (priv->phy)
> > +		return;
> > +
> > +	switch (interface) {
> > +	case PHY_INTERFACE_MODE_USXGMII:
> > +	case PHY_INTERFACE_MODE_10GBASER:
> > +	default:
> > +		xsi_sel = AIROHA_SCU_PCIE_XSI1_USXGMII;
> > +	}
> > +
> > +	regmap_update_bits(priv->scu, AIROHA_SCU_SSTR,
> > +			   AIROHA_SCU_PCIE_XSI1_SEL,
> > +			   xsi_sel);
> 
> I suspect the AI will be here soon. xsi_sel is initially a random
> stack value. IF interface is something else, you use that random value
> with regmap_update_bits().
>

Doesn't default address that case? Anyway PCS for PCIe here is quite
special...

It does support 2500BASE-X or 10G/USXGMII, but 2500base-x is handled by the
USB serdes and 10g is handled by the PCIe serdes and this is internally
handled by the SCU reg.

This is modelled by the presence of the PHY in DT.
- no PHY -> 10g
- PHY -> 2500base-x and configuration done by the USB PHY
 
> >  static const struct of_device_id airoha_pcs_of_table[] = {
> >  	{ .compatible = "airoha,an7581-pcs-eth", .data = &an7581_pcs_eth },
> >  	{ .compatible = "airoha,an7581-pcs-pon", .data = &an7581_pcs_pon },
> >  	{ .compatible = "airoha,an7581-pcs-pcie", .data = &an7581_pcs_pcie },
> >  	{ .compatible = "airoha,an7581-pcs-usb", .data = &an7581_pcs_usb },
> > +	{ .compatible = "airoha,an7583-pcs-eth", .data = &an7583_pcs_eth },
> > +	{ .compatible = "airoha,an7583-pcs-pon", .data = &an7583_pcs_pon },
> > +	{ .compatible = "airoha,an7583-pcs-pcie", .data = &an7583_pcs_pcie },
> > +	{ .compatible = "airoha,an7583-pcs-usb", .data = &an7583_pcs_usb },
> 
> Device tree binding update to list these new compatibles?

Yes since the AN7581 is still to be merged, I just posted the driver for
reference for anyone that is currently using AN7583 and the updated schema
will come when it will go out of RFC.

> 
> 	Andrew

-- 
	Ansuel

  reply	other threads:[~2026-09-25 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  7:27 Christian Marangi
2026-09-25 12:07 ` Andrew Lunn
2026-09-25 12:18   ` Christian Marangi [this message]
2026-09-25 12:43     ` Andrew Lunn
2026-09-25 12:10 ` Andrew Lunn
2026-09-25 12:21   ` Christian Marangi

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=6ab6669c.232cdbff.15fa39.f0d3@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®