From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"Russell King (Oracle)" <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, Eric Dumazet <edumazet@google.com>,
Vladimir Oltean <olteanv@gmail.com>,
kernel@pengutronix.de, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v1 4/5] net: dsa: microchip: ksz8: Prepare ksz8863_smi for regmap register access validation
Date: Wed, 24 May 2023 19:56:26 +0200 [thread overview]
Message-ID: <20230524175626.GC7074@pengutronix.de> (raw)
In-Reply-To: <584bb123-28c7-4d56-bad7-efcc2c343ecb@lunn.ch>
On Wed, May 24, 2023 at 06:59:28PM +0200, Andrew Lunn wrote:
> On Wed, May 24, 2023 at 02:32:19PM +0200, Oleksij Rempel wrote:
> > This patch prepares the ksz8863_smi part of ksz8 driver to utilize the
> > regmap register access validation feature.
> >
> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > ---
> > drivers/net/dsa/microchip/ksz8863_smi.c | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/drivers/net/dsa/microchip/ksz8863_smi.c b/drivers/net/dsa/microchip/ksz8863_smi.c
> > index 2af807db0b45..303a4707c759 100644
> > --- a/drivers/net/dsa/microchip/ksz8863_smi.c
> > +++ b/drivers/net/dsa/microchip/ksz8863_smi.c
> > @@ -104,6 +104,7 @@ static const struct regmap_config ksz8863_regmap_config[] = {
> > .cache_type = REGCACHE_NONE,
> > .lock = ksz_regmap_lock,
> > .unlock = ksz_regmap_unlock,
> > + .max_register = BIT(8) - 1,
>
> Maybe SZ_256 - 1 is more readable?
It is the same way used in other regmap_config in this driver.
As for me, U8_MAX is probably more understandable way, since addressing
since is 8bit.
> > },
> > {
> > .name = "#16",
> > @@ -113,6 +114,7 @@ static const struct regmap_config ksz8863_regmap_config[] = {
> > .cache_type = REGCACHE_NONE,
> > .lock = ksz_regmap_lock,
> > .unlock = ksz_regmap_unlock,
> > + .max_register = BIT(8) - 2,
>
> - 2?
>
> Is this the 16 bit regmap? So it has 1/2 the number of registers of
> the 8 bit regmap? So i would of thought it should be BIT(7)-1, or
> SZ_128-1 ?
Sorry, it is a typo.
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-05-24 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 12:32 [PATCH net-next v1 0/5] Microchip DSA Driver Improvements Oleksij Rempel
2023-05-24 12:32 ` [PATCH net-next v1 1/5] net: dsa: microchip: improving error handling for 8-bit register RMW operations Oleksij Rempel
2023-05-24 12:39 ` Russell King (Oracle)
2023-05-24 17:32 ` Oleksij Rempel
2023-05-24 12:32 ` [PATCH net-next v1 2/5] net: dsa: microchip: add an enum for regmap widths Oleksij Rempel
2023-05-24 17:03 ` Andrew Lunn
2023-05-24 17:53 ` Oleksij Rempel
2023-05-24 12:32 ` [PATCH net-next v1 3/5] net: dsa: microchip: remove ksz_port:on variable Oleksij Rempel
2023-05-24 16:51 ` Andrew Lunn
2023-05-24 12:32 ` [PATCH net-next v1 4/5] net: dsa: microchip: ksz8: Prepare ksz8863_smi for regmap register access validation Oleksij Rempel
2023-05-24 16:59 ` Andrew Lunn
2023-05-24 17:56 ` Oleksij Rempel [this message]
2023-05-24 12:32 ` [PATCH net-next v1 5/5] net: dsa: microchip: Add register access control for KSZ8873 chip Oleksij Rempel
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=20230524175626.GC7074@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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;
as well as URLs for NNTP newsgroup(s).