From: Tom Rini <trini@konsulko.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: u-boot@lists.denx.de, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH 2/3] clk: clk-cdce9xx.c: Change from u32 to ulong for addresses
Date: Mon, 14 Jul 2025 08:03:50 -0600 [thread overview]
Message-ID: <20250714140350.GD13084@bill-the-cat> (raw)
In-Reply-To: <f3ff27e4-106b-411d-89f0-82e7e78fff77@cherry.de>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
On Mon, Jul 14, 2025 at 12:35:14PM +0200, Quentin Schulz wrote:
> Hi Tom,
>
> On 7/2/25 3:05 AM, Tom Rini wrote:
> > For 32/64bit correctness, we need to use ulong and not u32 for casting
> > for addresses.
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > Cc: Lukasz Majewski <lukma@denx.de>
> > Cc: Sean Anderson <seanga2@gmail.com>
> > ---
> > drivers/clk/clk-cdce9xx.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/clk/clk-cdce9xx.c b/drivers/clk/clk-cdce9xx.c
> > index e5f74e714d54..afb997c06be5 100644
> > --- a/drivers/clk/clk-cdce9xx.c
> > +++ b/drivers/clk/clk-cdce9xx.c
> > @@ -103,7 +103,7 @@ static int cdce9xx_clk_probe(struct udevice *dev)
> > u32 val;
> > struct clk clk;
> > - val = (u32)dev_read_addr_ptr(dev);
> > + val = (ulong)dev_read_addr_ptr(dev);
>
> The output would be stored in a u32 anyway so not sure this actually helps
> (see type of val in the git context above).
>
> > ret = i2c_get_chip(dev->parent, val, 1, &data->i2c);
> > if (ret) {
> > @@ -226,10 +226,10 @@ static ulong cdce9xx_clk_set_rate(struct clk *clk, ulong rate)
> > }
> > static const struct udevice_id cdce9xx_clk_of_match[] = {
> > - { .compatible = "ti,cdce913", .data = (u32)&cdce913_chip_info },
> > - { .compatible = "ti,cdce925", .data = (u32)&cdce925_chip_info },
> > - { .compatible = "ti,cdce937", .data = (u32)&cdce937_chip_info },
> > - { .compatible = "ti,cdce949", .data = (u32)&cdce949_chip_info },
> > + { .compatible = "ti,cdce913", .data = (ulong)&cdce913_chip_info },
> > + { .compatible = "ti,cdce925", .data = (ulong)&cdce925_chip_info },
> > + { .compatible = "ti,cdce937", .data = (ulong)&cdce937_chip_info },
> > + { .compatible = "ti,cdce949", .data = (ulong)&cdce949_chip_info },
>
> Just get rid of the cast I guess? udevice_id.data being a ulong already the
> compiler should perform the cast in any case and this improves readability?
I'll take a harder look. This and maybe 1 or 3 other drivers are
following the above pattern. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-07-14 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 1:05 [PATCH 1/3] clk: Add missing <dm/device.h> to include/clk.h Tom Rini
2025-07-02 1:05 ` [PATCH 2/3] clk: clk-cdce9xx.c: Change from u32 to ulong for addresses Tom Rini
2025-07-14 10:35 ` Quentin Schulz
2025-07-14 14:03 ` Tom Rini [this message]
2025-07-17 15:08 ` Tom Rini
2025-07-17 15:19 ` Quentin Schulz
2025-07-17 18:05 ` Tom Rini
2025-07-02 1:05 ` [PATCH 3/3] clk: Tighten some clock driver dependencies Tom Rini
2025-10-28 23:57 ` (subset) [PATCH 1/3] clk: Add missing <dm/device.h> to include/clk.h Tom Rini
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=20250714140350.GD13084@bill-the-cat \
--to=trini@konsulko.com \
--cc=lukma@denx.de \
--cc=quentin.schulz@cherry.de \
--cc=seanga2@gmail.com \
--cc=u-boot@lists.denx.de \
/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