From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v1 1/1] regmap-irq: Consistently use memset32() in regmap_irq_thread()
Date: Wed, 25 Sep 2024 11:55:51 +0300 [thread overview]
Message-ID: <0b7b6ca3-b05b-40f2-86cf-083beb72727c@gmail.com> (raw)
In-Reply-To: <20240925082726.620622-1-andriy.shevchenko@linux.intel.com>
On 9/25/24 11:27, Andy Shevchenko wrote:
> The commit 4d60cac951fd ("regmap-irq: Add no_status support") adds
> an additional branch into IRQ thread handler in regmap. It wisely
> chose to use memset32() as it might be optimised on some architectures
> and hence give a performance benefit. At the same time the old code
> continue using simple memset(). Update the old code to use memset32().
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/base/regmap/regmap-irq.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/base/regmap/regmap-irq.c b/drivers/base/regmap/regmap-irq.c
> index a750e48a26b8..33ec28e3a802 100644
> --- a/drivers/base/regmap/regmap-irq.c
> +++ b/drivers/base/regmap/regmap-irq.c
> @@ -364,14 +364,11 @@ static irqreturn_t regmap_irq_thread(int irq, void *d)
> memset32(data->status_buf, GENMASK(31, 0), chip->num_regs);
> } else if (chip->num_main_regs) {
> unsigned int max_main_bits;
> - unsigned long size;
> -
> - size = chip->num_regs * sizeof(unsigned int);
>
> max_main_bits = (chip->num_main_status_bits) ?
> chip->num_main_status_bits : chip->num_regs;
> /* Clear the status buf as we don't read all status regs */
> - memset(data->status_buf, 0, size);
> + memset32(data->status_buf, 0, chip->num_regs);
>
> /* We could support bulk read for main status registers
> * but I don't expect to see devices with really many main
Thanks Andy.
Can we guarantee the sizeof(unsigned int) == sizeof(uint32_t) on all
supported architectures? (The status_buf is unsigned int, right?). If
yes, then this looks nice to me.
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2024-09-25 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 8:27 [PATCH v1 1/1] regmap-irq: Consistently use memset32() in regmap_irq_thread() Andy Shevchenko
2024-09-25 8:55 ` Matti Vaittinen [this message]
2024-09-25 9:02 ` Andy Shevchenko
2024-10-01 11:13 ` Mark Brown
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=0b7b6ca3-b05b-40f2-86cf-083beb72727c@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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