[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d04bd22-3d04-e75c-71ff-f1b67339b22e@gmail.com>
Date: Tue, 31 Aug 2021 13:55:05 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Linus Walleij <linus.walleij@...aro.org>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, DENG Qingfang <dqfext@...il.com>,
Mauri Sandberg <sandberg@...lfence.com>
Subject: Re: [PATCH net v2] net: dsa: tag_rtl4_a: Fix egress tags
On 8/31/2021 11:50 AM, Linus Walleij wrote:
> I noticed that only port 0 worked on the RTL8366RB since we
> started to use custom tags.
>
> It turns out that the format of egress custom tags is actually
> different from ingress custom tags. While the lower bits just
> contain the port number in ingress tags, egress tags need to
> indicate destination port by setting the bit for the
> corresponding port.
>
> It was working on port 0 because port 0 added 0x00 as port
> number in the lower bits, and if you do this the packet appears
> at all ports, including the intended port. Ooops.
>
> Fix this and all ports work again. Use the define for shifting
> the "type A" into place while we're at it.
>
> Tested on the D-Link DIR-685 by sending traffic to each of
> the ports in turn. It works.
>
> Fixes: 86dd9868b878 ("net: dsa: tag_rtl4_a: Support also egress tags")
> Cc: DENG Qingfang <dqfext@...il.com>
> Cc: Mauri Sandberg <sandberg@...lfence.com>
> Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
--
Florian
Powered by blists - more mailing lists