From: Lee Jones <lee@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org,
alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, mat.jonczyk@o2.pl,
dlan@gentoo.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, troymitchell988@gmail.com,
guodong@riscstar.com, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/8] mfd: simple-mfd-i2c: specify max_register
Date: Wed, 23 Jul 2025 10:51:25 +0100 [thread overview]
Message-ID: <20250723095125.GR11056@google.com> (raw)
In-Reply-To: <20250710175107.1280221-3-elder@riscstar.com>
On Thu, 10 Jul 2025, Alex Elder wrote:
> All devices supported by simple MFD use the same 8-bit register 8-bit
> value regmap configuration. There is an option available for a device
> to specify a custom configuration, but no existing device uses it.
>
> Rather than specify a "full" regmap configuration to change only
> the max_register value, Lee Jones suggested allowing max_register
> to be specified in the simple_mfd_data structure. If regmap_config
> and max_register are both supplied, the max_register field is ignored.
>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> Suggested-by: Lee Jones <lee@kernel.org>
> ---
> v8: - Use regmap_config_8r_8v, modifying it if max_register supplied
>
> drivers/mfd/simple-mfd-i2c.c | 8 ++++++--
> drivers/mfd/simple-mfd-i2c.h | 3 ++-
> 2 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mfd/simple-mfd-i2c.c b/drivers/mfd/simple-mfd-i2c.c
> index 22159913bea03..5138aa72140b5 100644
> --- a/drivers/mfd/simple-mfd-i2c.c
> +++ b/drivers/mfd/simple-mfd-i2c.c
> @@ -24,15 +24,16 @@
>
> #include "simple-mfd-i2c.h"
>
> -static const struct regmap_config regmap_config_8r_8v = {
> +static struct regmap_config regmap_config_8r_8v = {
> .reg_bits = 8,
> .val_bits = 8,
> + /* .max_register can be specified in simple_mfd_data */
Drop this comment please.
> };
>
> static int simple_mfd_i2c_probe(struct i2c_client *i2c)
> {
> const struct simple_mfd_data *simple_mfd_data;
> - const struct regmap_config *regmap_config;
> + struct regmap_config *regmap_config;
> struct regmap *regmap;
> int ret;
>
> @@ -43,8 +44,11 @@ static int simple_mfd_i2c_probe(struct i2c_client *i2c)
> regmap_config = ®map_config_8r_8v;
> else
> regmap_config = simple_mfd_data->regmap_config;
> + if (simple_mfd_data && !simple_mfd_data->regmap_config)
> + regmap_config->max_register = simple_mfd_data->max_register;
If max_register is set in simple_mfd_data, it should take precedence.
if (simple_mfd_data && simple_mfd_data->max_register)
regmap_config->max_register = simple_mfd_data->max_register;
> regmap = devm_regmap_init_i2c(i2c, regmap_config);
> + regmap_config->max_register = 0;
Does max_register definitely have persistence over subsequent calls?
> if (IS_ERR(regmap))
> return PTR_ERR(regmap);
>
> diff --git a/drivers/mfd/simple-mfd-i2c.h b/drivers/mfd/simple-mfd-i2c.h
> index 7cb2bdd347d97..ea2a96af8bce4 100644
> --- a/drivers/mfd/simple-mfd-i2c.h
> +++ b/drivers/mfd/simple-mfd-i2c.h
> @@ -24,7 +24,8 @@
> #include <linux/regmap.h>
>
> struct simple_mfd_data {
> - const struct regmap_config *regmap_config;
> + struct regmap_config *regmap_config;
> + unsigned int max_register; /* Ignored if regmap_config supplied */
> const struct mfd_cell *mfd_cell;
> size_t mfd_cell_size;
> };
> --
> 2.45.2
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-07-23 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 17:50 [PATCH v8 0/8] spacemit: introduce P1 PMIC support Alex Elder
2025-07-10 17:50 ` [PATCH v8 1/8] dt-bindings: mfd: add support the SpacemiT P1 PMIC Alex Elder
2025-07-10 17:51 ` [PATCH v8 2/8] mfd: simple-mfd-i2c: specify max_register Alex Elder
2025-07-23 9:51 ` Lee Jones [this message]
2025-07-23 12:42 ` Alex Elder
2025-07-24 10:14 ` Lee Jones
2025-07-10 17:51 ` [PATCH v8 3/8] mfd: simple-mfd-i2c: add SpacemiT P1 support Alex Elder
2025-07-10 17:51 ` [PATCH v8 4/8] regulator: spacemit: support SpacemiT P1 regulators Alex Elder
2025-07-10 17:51 ` [PATCH v8 5/8] rtc: spacemit: support the SpacemiT P1 RTC Alex Elder
2025-07-23 21:39 ` Alexandre Belloni
2025-07-23 23:37 ` Alex Elder
2025-07-10 17:51 ` [PATCH v8 6/8] riscv: dts: spacemit: enable the i2c8 adapter Alex Elder
2025-07-10 17:51 ` [PATCH v8 7/8] riscv: dts: spacemit: define fixed regulators Alex Elder
2025-07-10 17:51 ` [PATCH v8 8/8] riscv: dts: spacemit: define regulator constraints Alex Elder
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=20250723095125.GR11056@google.com \
--to=lee@kernel.org \
--cc=alex@ghiti.fr \
--cc=alexandre.belloni@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troymitchell988@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;
as well as URLs for NNTP newsgroup(s).