From: Alex Elder <elder@riscstar.com>
To: Lee Jones <lee@kernel.org>
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,
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 v4 2/7] mfd: simple-mfd-i2c: add SpacemiT P1 support
Date: Fri, 27 Jun 2025 08:36:39 -0500 [thread overview]
Message-ID: <0eda5bf4-ce63-43da-9c2f-7d4ec902758c@riscstar.com> (raw)
In-Reply-To: <20250627125119.GF10134@google.com>
On 6/27/25 7:51 AM, Lee Jones wrote:
>> @@ -93,12 +93,30 @@ static const struct simple_mfd_data maxim_mon_max77705 = {
>> .mfd_cell_size = ARRAY_SIZE(max77705_sensor_cells),
>> };
>>
>> +static const struct regmap_config spacemit_p1_regmap_config = {
>> + .reg_bits = 8,
>> + .val_bits = 8,
>> + .max_register = 0xaa,
>> +};
> Suggest making this more widely useful by adding the 'max_register'
> attribute to 'struct simple_mfd' and conditionally overriding
> regmap_config_8r_8v's value during probe.
So you're suggesting I make a general improvement to
"simple-mfd-i2c.c", because everybody else just uses
the generic fallback regmap config?
(I'm asking because at first I didn't understand your
statement, and the "more widely useful" comment).
I would be happy to do this, and it's not that hard.
Can I do it as a follow-on patch though? It's adding
scope (again), beyond what I anticipated and honestly
I'm ready to be done with this...
Anyway, if you say "no" I'll send another version of
this series today.
-Alex
>
>> +static const struct mfd_cell spacemit_p1_cells[] = {
>> + { .name = "spacemit-p1-regulator", },
>> + { .name = "spacemit-p1-rtc", },
>> +};
>> +
next prev parent reply other threads:[~2025-06-27 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 16:41 [PATCH v4 0/7] spacemit: introduce P1 PMIC support Alex Elder
2025-06-25 16:41 ` [PATCH v4 1/7] dt-bindings: mfd: add support the SpacemiT P1 PMIC Alex Elder
2025-06-25 16:41 ` [PATCH v4 2/7] mfd: simple-mfd-i2c: add SpacemiT P1 support Alex Elder
2025-06-27 12:51 ` Lee Jones
2025-06-27 13:36 ` Alex Elder [this message]
2025-07-01 11:07 ` Lee Jones
2025-06-25 16:41 ` [PATCH v4 3/7] regulator: spacemit: support SpacemiT P1 regulators Alex Elder
2025-06-25 16:41 ` [PATCH v4 4/7] rtc: spacemit: support the SpacemiT P1 RTC Alex Elder
2025-06-25 22:01 ` Alexandre Belloni
2025-06-25 22:10 ` Alex Elder
2025-06-25 16:41 ` [PATCH v4 5/7] riscv: dts: spacemit: enable the i2c8 adapter Alex Elder
2025-06-25 16:41 ` [PATCH v4 6/7] riscv: dts: spacemit: define fixed regulators Alex Elder
2025-06-25 16:41 ` [PATCH v4 7/7] 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=0eda5bf4-ce63-43da-9c2f-7d4ec902758c@riscstar.com \
--to=elder@riscstar.com \
--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=krzk+dt@kernel.org \
--cc=lee@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