Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: 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>,
	 Matti Vaittinen <mazziesaccount@gmail.com>,
	Xu Yilun <yilun.xu@intel.com>,  Tom Rix <trix@redhat.com>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	 Andy Shevchenko <andy@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	 Tim Harvey <tharvey@gateworks.com>,
	Orson Zhai <orsonzhai@gmail.com>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>,
	 Chunyan Zhang <zhang.lyra@gmail.com>
Cc: linux-kernel@vger.kernel.org, imx@lists.linux.dev,
	 linux-arm-kernel@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,  linux-omap@vger.kernel.org,
	 Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: [PATCH v2 06/24] mfd: rohm-bd9576: Constify read-only regmap structs
Date: Thu, 04 Jul 2024 19:23:16 +0200	[thread overview]
Message-ID: <20240704-mfd-const-regmap_config-v2-6-0c8785b1331d@gmail.com> (raw)
In-Reply-To: <20240704-mfd-const-regmap_config-v2-0-0c8785b1331d@gmail.com>

`bd957x_regmap`, `bd9576_irqs` and `bd9576_irq_chip` are 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 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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),

-- 
2.40.1


  parent reply	other threads:[~2024-07-04 17:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 17:23 [PATCH v2 00/24] mfd: Constify read-only regmap structs Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 01/24] mfd: da9062-core: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 02/24] mfd: fsl-imx25-tsadc: Constify struct regmap_config Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 03/24] mfd: hi655x-pmic: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 04/24] mfd: wcd934x: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 05/24] mfd: tps6105x: " Javier Carrasco
2024-07-04 17:23 ` Javier Carrasco [this message]
2024-07-05  4:54   ` [PATCH v2 06/24] mfd: rohm-bd9576: Constify read-only regmap structs Matti Vaittinen
2024-07-04 17:23 ` [PATCH v2 07/24] mfd: intel-m10-bmc: Constify struct regmap_config Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 08/24] mfd: 88pm80x: Constify read-only regmap structs Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 09/24] mfd: bd9571mwv: Constify struct regmap_irq_chip Javier Carrasco
2024-07-05  5:50   ` Matti Vaittinen
2024-07-04 17:23 ` [PATCH v2 10/24] mfd: intel_soc_pmic_bxtwc: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 11/24] mfd: retu: Constify read-only regmap structs Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 12/24] mfd: rk8xx-core: Constify struct regmap_irq_chip Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 13/24] mfd: rohm-bd71828: Constify read-only regmap structs Javier Carrasco
2024-07-05  5:47   ` Matti Vaittinen
2024-07-04 17:23 ` [PATCH v2 14/24] mfd: rohm-bd718x7: Constify struct regmap_irq_chip Javier Carrasco
2024-07-05  5:48   ` Matti Vaittinen
2024-07-04 17:23 ` [PATCH v2 15/24] mfd: tps65086: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 16/24] mfd: tps65090: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 17/24] mfd: tps65218: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 18/24] mfd: tps65219: Constify read-only regmap structs Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 19/24] mfd: tps65910: Constify struct regmap_irq_chip Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 20/24] mfd: tps65912: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 21/24] mfd: twl6040: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 22/24] mfd: gateworks-gsc: Constify struct regmap_bus Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 23/24] mfd: mc13xxx-spi: " Javier Carrasco
2024-07-04 17:23 ` [PATCH v2 24/24] mfd: sprd-sc27xx-spi: " Javier Carrasco
2024-07-05  1:11   ` Baolin Wang
2024-07-25  7:38 ` [PATCH v2 00/24] mfd: Constify read-only regmap structs Lee Jones

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=20240704-mfd-const-regmap_config-v2-6-0c8785b1331d@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=andy@kernel.org \
    --cc=baolin.wang@linux.alibaba.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=linux-omap@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=mazziesaccount@gmail.com \
    --cc=orsonzhai@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=support.opensource@diasemi.com \
    --cc=tharvey@gateworks.com \
    --cc=tony@atomide.com \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    --cc=zhang.lyra@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