From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Cong Dang <cong.dang.xn@renesas.com>,
Hai Pham <hai.pham.ud@renesas.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] memory: renesas-rpc-if: Fix PHYCNT.STRTIM setting
Date: Fri, 27 Jan 2023 09:30:45 +0100 [thread overview]
Message-ID: <Y9OLtbN5uhyPYxyj@ninjato> (raw)
In-Reply-To: <CAMuHMdX6epwBa9fT9MoU=oC9k6YV2L9NXOEd84QkLnSr2vkDBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
> > - rpc->type = (uintptr_t)of_device_get_match_data(dev);
> > + rpc->size = resource_size(res);
>
> Nit: No need to move the initialization of rpc->size.
True. It is more cosmetic to have all rpc->* inits in one block. But I
think it is worth it.
> > + regmap_update_bits(rpc->regmap, RPCIF_PHYCNT,
> > + /* create mask with all affected bits set */
> > + RPCIF_PHYCNT_STRTIM(BIT(fls(rpc->info->strtim)) - 1),
>
> Note that this relies on the strtim value being 4 or higher.
> As this value is not user-configurable, but fixed in the driver,
> it's probably OK.
If there was a chance that newer SoCs use such a value, I'd go for the
seperate mask. But I am confident this time has passed and the next
value is likely >15.
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-27 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:35 Wolfram Sang
2023-01-27 8:17 ` Geert Uytterhoeven
2023-01-27 8:30 ` Wolfram Sang [this message]
2023-01-27 10:44 ` Lad, Prabhakar
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=Y9OLtbN5uhyPYxyj@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=cong.dang.xn@renesas.com \
--cc=geert@linux-m68k.org \
--cc=hai.pham.ud@renesas.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.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
all inboxes | Powered by JetHome®