From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Support Opensource <support.opensource@diasemi.com>,
Lee Jones <lee@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Xu Yilun <yilun.xu@intel.com>,
Tom Rix <trix@redhat.com>
Cc: linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/7] mfd: rohm-bd9576: Constify struct regmap_config
Date: Thu, 4 Jul 2024 11:03:00 +0200 [thread overview]
Message-ID: <c83ef39f-2267-4d02-9d77-65baa5a026c1@gmail.com> (raw)
In-Reply-To: <0acd9da5-80ec-4a45-b00a-8e28ab4e345a@gmail.com>
On 04/07/2024 06:50, Matti Vaittinen wrote:
> On 7/3/24 18:37, Javier Carrasco wrote:
>> `bd957x_regmap` is not modified and can be declared as const
>> to move its data to a read-only section.
>>
>> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
>> ---
>> drivers/mfd/rohm-bd9576.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/mfd/rohm-bd9576.c b/drivers/mfd/rohm-bd9576.c
>> index 3a9f61961721..634c65c7d108 100644
>> --- a/drivers/mfd/rohm-bd9576.c
>> +++ b/drivers/mfd/rohm-bd9576.c
>> @@ -57,7 +57,7 @@ static const struct regmap_access_table
>> volatile_regs = {
>> .n_yes_ranges = ARRAY_SIZE(volatile_ranges),
>> };
>> -static struct regmap_config bd957x_regmap = {
>> +static const struct regmap_config bd957x_regmap = {
>> .reg_bits = 8,
>> .val_bits = 8,
>> .volatile_table = &volatile_regs,
>>
>
> Thanks a ton Javier. This looks good to me but if you feel like going an
> extra mile while you are at it... Do you think this could be extended to:
>
>
> diff --git a/drivers/mfd/rohm-bd9576.c b/drivers/mfd/rohm-bd9576.c
> index 3a9f61961721..17323ae39803 100644
> --- a/drivers/mfd/rohm-bd9576.c
> +++ b/drivers/mfd/rohm-bd9576.c
> @@ -57,7 +57,7 @@ static const struct regmap_access_table volatile_regs = {
> .n_yes_ranges = ARRAY_SIZE(volatile_ranges),
> };
>
> -static struct regmap_config bd957x_regmap = {
> +static const struct regmap_config bd957x_regmap = {
> .reg_bits = 8,
> .val_bits = 8,
> .volatile_table = &volatile_regs,
> @@ -65,7 +65,7 @@ static struct regmap_config bd957x_regmap = {
> .cache_type = REGCACHE_MAPLE,
> };
>
> -static struct regmap_irq bd9576_irqs[] = {
> +static const struct regmap_irq bd9576_irqs[] = {
> REGMAP_IRQ_REG(BD9576_INT_THERM, 0, BD957X_MASK_INT_MAIN_THERM),
> REGMAP_IRQ_REG(BD9576_INT_OVP, 0, BD957X_MASK_INT_MAIN_OVP),
> REGMAP_IRQ_REG(BD9576_INT_SCP, 0, BD957X_MASK_INT_MAIN_SCP),
> @@ -76,7 +76,7 @@ static struct regmap_irq bd9576_irqs[] = {
> REGMAP_IRQ_REG(BD9576_INT_SYS, 0, BD957X_MASK_INT_MAIN_SYS),
> };
>
> -static struct regmap_irq_chip bd9576_irq_chip = {
> +static const struct regmap_irq_chip bd9576_irq_chip = {
> .name = "bd9576_irq",
> .irqs = &bd9576_irqs[0],
> .num_irqs = ARRAY_SIZE(bd9576_irqs),
>
>
> Yours,
> -- Matti
>
Sure, I will generalize it and update the series to cover regmap_irq and
regmap_irq_chip as well, of course including these two cases too.
Best regards,
Javier Carrasco
next prev parent reply other threads:[~2024-07-04 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 15:37 [PATCH 0/7] mfd: Constify struct regmap_config Javier Carrasco
2024-07-03 15:37 ` [PATCH 1/7] mfd: da9062-core: " Javier Carrasco
2024-07-03 15:37 ` [PATCH 2/7] mfd: fsl-imx25-tsadc: " Javier Carrasco
2024-07-03 15:37 ` [PATCH 3/7] mfd: hi655x-pmic: " Javier Carrasco
2024-07-03 15:37 ` [PATCH 4/7] mfd: wcd934x: " Javier Carrasco
2024-07-03 15:37 ` [PATCH 5/7] mfd: tps6105x: " Javier Carrasco
2024-07-03 15:37 ` [PATCH 6/7] mfd: rohm-bd9576: " Javier Carrasco
2024-07-04 4:50 ` Matti Vaittinen
2024-07-04 9:03 ` Javier Carrasco [this message]
2024-07-03 15:37 ` [PATCH 7/7] mfd: intel-m10-bmc: " Javier Carrasco
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=c83ef39f-2267-4d02-9d77-65baa5a026c1@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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