From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, <linux-omap@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<srk@ti.com>, Pekka Varis <p-varis@ti.com>
Subject: Re: [PATCH net-next 2/2] net: ethernet: ti: am65-cpsw: enable DSCP to priority map for RX
Date: Fri, 8 Nov 2024 20:12:40 +0530 [thread overview]
Message-ID: <208a1472-c69b-4c20-9bb2-25158edfd7d8@ti.com> (raw)
In-Reply-To: <7ae1ccf9-67c0-45ba-9cb9-886701adb488@kernel.org>
On Fri, Nov 08, 2024 at 02:55:18PM +0200, Roger Quadros wrote:
> Hi Siddharth,
>
> On 08/11/2024 14:30, Siddharth Vadapalli wrote:
[...]
> >> +#define AM65_CPSW_PORTN_REG_CTL 0x004
> >
> > nitpick: indentation needs to be fixed here to align with the macros
> > below.
>
> It is fine in the code and in my editor in this reply email.
That's strange. But it appears the same to me as seen at:
https://lore.kernel.org/r/20241105-am65-cpsw-multi-rx-dscp-v1-2-38db85333c88@kernel.org/
where the indentation looks incorrect.
[...]
>
> >> +
> >> + if (dscp > AM65_CPSW_DSCP_MAX)
> >> + return -EINVAL;
> >
> > am65_cpsw_port_set_dscp_map() seems to be invoked by
> > am65_cpsw_port_enable_dscp_map() below, where the above check is guaranteed
> > to be satisfied. Is the check added for future-proofing this function?
> >
>
> Right, future callers can't be guaranteed to do the check so I'd prefer
> to have the check here.
Thank you for the confirmation.
>
> >> +
> >> + if (pri > AM65_CPSW_PRI_MAX)
> >> + return -EINVAL;
> >> +
> >> + reg_ofs = (dscp / 8) * 4; /* reg offset to this dscp */
> >> + bit_ofs = 4 * (dscp % 8); /* bit offset to this dscp */
> >
> > Maybe a macro can be used for the "4" since it is not clear what it
>
> First 4 was for 4 bytes per register. Not sure if we need a macro for this.
> The comment already mentions register offset and we know each register is
> 32-bits wide.
>
> We could add a macro for the 8 though
> #define AM65_CPSW_DSCP_PRI_PER_REG 8
>
> The second 4 is actually 4 bits per DSCP field. I could add a macro for this.
> #define AM65_CPSW_DSCP_PRI_FIELD_WIDTH 4
This looks good to me, but I am fine either way, in case you prefer to
drop the macros.
>
>
> > corresponds to. Or maybe two macros can be used for "reg_ofs" and
> > "bit_ofs".
> >
> >> + val = readl(slave->port_base + AM65_CPSW_PORTN_REG_DSCP_MAP + reg_ofs);
> >> + val &= ~(AM65_CPSW_PRI_MAX << bit_ofs); /* clear */
> >> + val |= pri << bit_ofs; /* set */
> >> + writel(val, slave->port_base + AM65_CPSW_PORTN_REG_DSCP_MAP + reg_ofs);
> >> + val = readl(slave->port_base + AM65_CPSW_PORTN_REG_DSCP_MAP + reg_ofs);
> >
> > The above readback seems to be just to flush the writel(). A comment of
> > the form:
> > /* flush */
> > might help, considering that other drivers do the same. Also, assigning
> > the returned value to "val" might not be required unless it is intended to
> > be checked.
>
> This was actually left over debug code. I'll drop the readl.
Ok.
Regards,
Siddharth.
next prev parent reply other threads:[~2024-11-08 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 14:18 [PATCH net-next 0/2] net: ethernet: ti: am65-cpsw: enable DSCP to priority map for RX Roger Quadros
2024-11-05 14:18 ` [PATCH net-next 1/2] net: ethernet: ti: am65-cpsw: update pri_thread_map as per IEEE802.1Q-2004 Roger Quadros
2024-11-06 5:22 ` Siddharth Vadapalli
2024-11-06 8:51 ` Roger Quadros
2024-11-05 14:18 ` [PATCH net-next 2/2] net: ethernet: ti: am65-cpsw: enable DSCP to priority map for RX Roger Quadros
2024-11-08 12:30 ` Siddharth Vadapalli
2024-11-08 12:55 ` Roger Quadros
2024-11-08 14:42 ` Siddharth Vadapalli [this message]
2024-11-09 10:31 ` Roger Quadros
2024-11-11 5:22 ` Siddharth Vadapalli
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=208a1472-c69b-4c20-9bb2-25158edfd7d8@ti.com \
--to=s-vadapalli@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p-varis@ti.com \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=srk@ti.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