From: David Laight <david.laight.linux@gmail.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
greghk@linuxfoundation.org, dlechner@baylibre.com,
nono.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] iio: frequency: ad983x: replace do_div() with div64_ul().
Date: Thu, 9 Apr 2026 22:46:09 +0100 [thread overview]
Message-ID: <20260409224609.3e36a208@pumpkin> (raw)
In-Reply-To: <CALoEA-yVCyyiA1gUCj4Z0JcLscpSSssPCPXnUPOciWJOHj3VUg@mail.gmail.com>
On Thu, 9 Apr 2026 21:58:20 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> On Thu, 9 Apr 2026 at 19:27, David Laight <david.laight.linux@gmail.com> wrote:
> > Except here you have clock frequencies.
> > Either they fit in 32bits or they don't.
> > So the value shouldn't be 'unsigned long', but either u32 or u64.
>
> The clk struct in linux/clk.h explicitly uses an unsigned long to represent
> the clock value, which is used in this driver. Using an unsigned long
> ensures platform independent usage without type mismatching.
Not really.
I've NFI why the the clock API using 'unsigned long'.
It almost certainly predates 64bit and any real idea that a clock might
exceed 4.2GHz.
It might even come from someone who wrote 16bit windows code and wanted
to ensure it was actually 32bit.
For 'platform portability' clocks are limited to 32bits so the 32bit
divide is fine.
If the clock could exceed 4.2G then you'd have to use u64 throughout.
>
> > You need to check the domain of the values, coccinelle is just looking
> > at the types.
> > Even with mclk being 'unsigned long' the code is fine provided the
> > frequency is below 4.2GHz.
>
> I agree that we're not dealing with potential truncation problems, however
> changing to div64_ul aligns the types with the clk API and scrubs a perfectly
> valid cocci error.
cocci only does type checking, it doesn't know the domain of the values.
So in this case it is almost certainly a false positive.
David
next prev parent reply other threads:[~2026-04-09 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:18 [PATCH] iio: frequency: ad983x: replace do_div() with div64_ul() Joshua Crofts
2026-04-09 13:34 ` Joshua Crofts
2026-04-09 14:52 ` Greg KH
2026-04-09 15:01 ` [PATCH v2] " Joshua Crofts
2026-04-09 15:39 ` David Lechner
2026-04-09 15:50 ` Andy Shevchenko
2026-04-09 15:49 ` [PATCH] " Andy Shevchenko
2026-04-09 17:27 ` David Laight
2026-04-09 19:58 ` Joshua Crofts
2026-04-09 21:46 ` David Laight [this message]
2026-04-10 4:30 ` Andy Shevchenko
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=20260409224609.3e36a208@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=greghk@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nono.sa@analog.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