From: Florian Fainelli <f.fainelli@gmail.com>
To: "Måns Rullgård" <mans@mansr.com>,
netdev@vger.kernel.org,
"Egil Hjelmeland" <privat@egil-hjelmeland.no>,
"Vladimir Oltean" <olteanv@gmail.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Juergen Borleis" <jbe@pengutronix.de>,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
lorenzo@kernel.org
Subject: Re: DSA using cpsw and lan9303
Date: Mon, 14 Feb 2022 09:16:10 -0800 [thread overview]
Message-ID: <d19abc0a-4685-514d-387b-ac75503ee07a@gmail.com> (raw)
In-Reply-To: <yw1x8rud4cux.fsf@mansr.com>
+others,
netdev is a high volume list, you should probably copy directly the
people involved with the code you are working with.
On 2/14/22 8:44 AM, Måns Rullgård wrote:
> The hardware I'm working on has a LAN9303 switch connected to the
> Ethernet port of an AM335x (ZCE package). In trying to make DSA work
> with this combination, I have encountered two problems.
>
> Firstly, the cpsw driver configures the hardware to filter out frames
> with unknown VLAN tags. To make it accept the tagged frames coming from
> the LAN9303, I had to modify the latter driver like this:
>
> diff --git a/drivers/net/dsa/lan9303-core.c b/drivers/net/dsa/lan9303-core.c
> index 2de67708bbd2..460c998c0c33 100644
> --- a/drivers/net/dsa/lan9303-core.c
> +++ b/drivers/net/dsa/lan9303-core.c
> @@ -1078,20 +1079,28 @@ static int lan9303_port_enable(struct dsa_switch *ds, int port,
> struct phy_device *phy)
> {
> struct lan9303 *chip = ds->priv;
> + struct net_device *master;
>
> if (!dsa_is_user_port(ds, port))
> return 0;
>
> + master = dsa_to_port(chip->ds, 0)->master;
> + vlan_vid_add(master, htons(ETH_P_8021Q), port);
That looks about right given that net/dsa/tag_lan9303.c appears to be a
quasi DSA_TAG_PROTO_8021Q implementation AFAICT.
> +
> return lan9303_enable_processing_port(chip, port);
> }
>
> Secondly, the cpsw driver strips VLAN tags from incoming frames, and
> this prevents the DSA parsing from working. As a dirty workaround, I
> did this:
>
> diff --git a/drivers/net/ethernet/ti/cpsw_priv.c b/drivers/net/ethernet/ti/cpsw_priv.c
> index 424e644724e4..e15f42ece8bf 100644
> --- a/drivers/net/ethernet/ti/cpsw_priv.c
> +++ b/drivers/net/ethernet/ti/cpsw_priv.c
> @@ -235,6 +235,7 @@ void cpsw_rx_vlan_encap(struct sk_buff *skb)
>
> /* Remove VLAN header encapsulation word */
> skb_pull(skb, CPSW_RX_VLAN_ENCAP_HDR_SIZE);
> + return;
>
> pkt_type = (rx_vlan_encap_hdr >>
> CPSW_RX_VLAN_ENCAP_HDR_PKT_TYPE_SHIFT) &
>
> With these changes, everything seems to work as expected.
>
> Now I'd appreciate if someone could tell me how I should have done this.
> Please don't make me send an actual patch.
--
Florian
next prev parent reply other threads:[~2022-02-14 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 16:44 DSA using cpsw and lan9303 Måns Rullgård
2022-02-14 17:16 ` Florian Fainelli [this message]
2022-02-14 17:43 ` Vladimir Oltean
2022-02-14 19:17 ` Måns Rullgård
2022-02-15 20:54 ` Vladimir Oltean
2022-02-16 13:17 ` Måns Rullgård
2022-02-16 14:15 ` Vladimir Oltean
2022-02-16 14:23 ` Måns Rullgård
2022-02-16 14:26 ` Vladimir Oltean
2022-02-16 17:00 ` Vladimir Oltean
2022-02-16 17:47 ` Måns Rullgård
2022-02-16 17:55 ` Vladimir Oltean
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=d19abc0a-4685-514d-387b-ac75503ee07a@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=grygorii.strashko@ti.com \
--cc=jbe@pengutronix.de \
--cc=lorenzo@kernel.org \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=privat@egil-hjelmeland.no \
/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).