From: "Måns Rullgård" <mans@mansr.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org,
Egil Hjelmeland <privat@egil-hjelmeland.no>,
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 19:17:33 +0000 [thread overview]
Message-ID: <yw1xtud12r76.fsf@mansr.com> (raw)
In-Reply-To: <20220214174349.6t3y7mwhqxaem3e7@skbuf> (Vladimir Oltean's message of "Mon, 14 Feb 2022 19:43:49 +0200")
Vladimir Oltean <olteanv@gmail.com> writes:
> Hi Måns,
>
> On Mon, Feb 14, 2022 at 09:16:10AM -0800, Florian Fainelli wrote:
>> +others,
>>
>> netdev is a high volume list, you should probably copy directly the
>> people involved with the code you are working with.
>
> Thanks, Florian.
>
>> > 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.
>
> Assuming cpsw_rx_vlan_encap() doesn't just eat the VLAN, but puts it in
> the skb hwaccel area. The tag_lan9303.c tagger must deal with both
> variants of VLANs.
>
> For example, dsa_8021q_rcv() has:
>
> skb_push_rcsum(skb, ETH_HLEN);
> if (skb_vlan_tag_present(skb)) {
> tci = skb_vlan_tag_get(skb);
> __vlan_hwaccel_clear_tag(skb);
> } else {
> __skb_vlan_pop(skb, &tci);
> }
> skb_pull_rcsum(skb, ETH_HLEN);
>
> vid = tci & VLAN_VID_MASK;
>
> (process @vid here)
>
> which should give you a head start.
Thanks, that looks promising.
>> > Please don't make me send an actual patch.
>
> So what is your plan otherwise? :)
I meant I didn't want to send a patch I know to be broken only to
provoke a discussion.
--
Måns Rullgård
next prev parent reply other threads:[~2022-02-14 20:52 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
2022-02-14 17:43 ` Vladimir Oltean
2022-02-14 19:17 ` Måns Rullgård [this message]
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=yw1xtud12r76.fsf@mansr.com \
--to=mans@mansr.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=jbe@pengutronix.de \
--cc=lorenzo@kernel.org \
--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).