From: Simon Horman <horms@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Thorsten Blum <thorsten.blum@toblux.com>,
marcin.s.wojtas@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: mvpp2: Improve data types and use min()
Date: Mon, 15 Jul 2024 19:39:22 +0100 [thread overview]
Message-ID: <20240715183922.GA263242@kernel.org> (raw)
In-Reply-To: <ZpVDVHXh4FTZnmUv@shell.armlinux.org.uk>
On Mon, Jul 15, 2024 at 04:44:01PM +0100, Russell King (Oracle) wrote:
> On Thu, Jul 11, 2024 at 05:47:43PM +0200, Thorsten Blum wrote:
> > Change the data type of the variable freq in mvpp2_rx_time_coal_set()
> > and mvpp2_tx_time_coal_set() to u32 because port->priv->tclk also has
> > the data type u32.
> >
> > Change the data type of the function parameter clk_hz in
> > mvpp2_usec_to_cycles() and mvpp2_cycles_to_usec() to u32 accordingly
> > and remove the following Coccinelle/coccicheck warning reported by
> > do_div.cocci:
> >
> > WARNING: do_div() does a 64-by-32 division, please consider using div64_ul instead
> >
> > Use min() to simplify the code and improve its readability.
> >
> > Compile-tested only.
> >
> > Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
>
> I'm still on holiday, but it's a wet day today. Don't expect replies
> from me to be regular.
>
> I don't think this is a good idea.
>
> priv->tclk comes from clk_get_rate() which returns an unsigned long.
> tclk should _also_ be an unsigned long, not a u32, so that the range
> of values clk_get_rate() returns can be represented without being
> truncted.
>
> Thus the use of unsigned long elsewhere where tclk is passed into is
> actually correct.
>
> If we need to limit tclk to values that u32 can represent, then that
> needs to be done here:
>
> priv->tclk = clk_get_rate(priv->pp_clk);
>
> by assigning the return value to an unsigned long local variable,
> then checking its upper liit before assigning it to priv->tclk.
Sorry, I thought that I had checked the types.
But clearly I wasn't nearly careful enough.
next prev parent reply other threads:[~2024-07-15 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 15:47 [PATCH net-next] net: mvpp2: Improve data types and use min() Thorsten Blum
2024-07-12 18:25 ` Simon Horman
2024-07-13 22:50 ` patchwork-bot+netdevbpf
2024-07-15 15:44 ` Russell King (Oracle)
2024-07-15 16:07 ` Jakub Kicinski
2024-07-15 18:39 ` Simon Horman [this message]
2024-07-16 17:48 ` Thorsten Blum
2024-07-17 12:30 ` David Laight
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=20240715183922.GA263242@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcin.s.wojtas@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thorsten.blum@toblux.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).