From: Alex Elder <elder@riscstar.com>
To: Troy Mitchell <troy.mitchell@linux.spacemit.com>,
lee@kernel.org, lgirdwood@gmail.com, broonie@kernel.org,
alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: mat.jonczyk@o2.pl, dlan@gentoo.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
linux.amoon@gmail.com, 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 v12 2/7] mfd: simple-mfd-i2c: add SpacemiT P1 support
Date: Mon, 25 Aug 2025 11:08:45 -0500 [thread overview]
Message-ID: <b387ebdd-ae5d-4711-9e10-c61cb06f4b5b@riscstar.com> (raw)
In-Reply-To: <089D29348F246F2C+aJ6bPgJsp5GjhDs5@LT-Guozexi>
On 8/14/25 9:28 PM, Troy Mitchell wrote:
> Hi, Alex,
>
> I did not find any accesses to the P1 shutdown or reboot registers here.
> Does this mean that the current series does not support reboot or shutdown?
Yes, that is correct.
> If so, do you have any plans to support this functionality?
At this time I personally don't have any plans to add this, but
it could be added later (by anyone).
I actually attempted to do this initially, but gave up. The PMIC
is accessed via I2C, and I needed to implement a non-blocking
version of the I2C register write operation. I tried that, but
then found that the shutdown or reboot still did not work reliably.
As it was, this was more than I originally planned to do, so I just
implemented the simple RTC operations instead.
-Alex
> If I have misunderstood, please correct me.
>
> Best regards,
> Troy
>
>
> On Tue, Aug 12, 2025 at 09:45:03PM -0500, Alex Elder wrote:
>> Enable support for the RTC and regulators found in the SpacemiT P1
>> PMIC. Support is implemented by the simple I2C MFD driver.
>>
>> The P1 PMIC is normally implemented with the SpacemiT K1 SoC. This
>> PMIC provides 6 buck converters and 12 LDO regulators. It also
>> implements a switch, watchdog timer, real-time clock, and more.
>> Initially its RTC and regulators are supported.
>>
>> Signed-off-by: Alex Elder <elder@riscstar.com>
>> ---
>> drivers/mfd/Kconfig | 11 +++++++++++
>> drivers/mfd/simple-mfd-i2c.c | 18 ++++++++++++++++++
>> 2 files changed, 29 insertions(+)
>>
>> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
>> index 425c5fba6cb1e..4d6a5a3a27220 100644
>> --- a/drivers/mfd/Kconfig
>> +++ b/drivers/mfd/Kconfig
>> @@ -1238,6 +1238,17 @@ config MFD_QCOM_RPM
>> Say M here if you want to include support for the Qualcomm RPM as a
>> module. This will build a module called "qcom_rpm".
>>
>> +config MFD_SPACEMIT_P1
>> + tristate "SpacemiT P1 PMIC"
>> + depends on I2C
>> + select MFD_SIMPLE_MFD_I2C
>> + help
>> + This option supports the I2C-based SpacemiT P1 PMIC, which
>> + contains regulators, a power switch, GPIOs, an RTC, and more.
>> + This option is selected when any of the supported sub-devices
>> + is configured. The basic functionality is implemented by the
>> + simple MFD I2C driver.
>> +
>> config MFD_SPMI_PMIC
>> tristate "Qualcomm SPMI PMICs"
>> depends on ARCH_QCOM || COMPILE_TEST
>> diff --git a/drivers/mfd/simple-mfd-i2c.c b/drivers/mfd/simple-mfd-i2c.c
>> index 22159913bea03..47ffaac035cae 100644
>> --- a/drivers/mfd/simple-mfd-i2c.c
>> +++ b/drivers/mfd/simple-mfd-i2c.c
>> @@ -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,
>> +};
>> +
>> +static const struct mfd_cell spacemit_p1_cells[] = {
>> + { .name = "spacemit-p1-regulator", },
>> + { .name = "spacemit-p1-rtc", },
>> +};
>> +
>> +static const struct simple_mfd_data spacemit_p1 = {
>> + .regmap_config = &spacemit_p1_regmap_config,
>> + .mfd_cell = spacemit_p1_cells,
>> + .mfd_cell_size = ARRAY_SIZE(spacemit_p1_cells),
>> +};
>> +
>> static const struct of_device_id simple_mfd_i2c_of_match[] = {
>> { .compatible = "kontron,sl28cpld" },
>> { .compatible = "silergy,sy7636a", .data = &silergy_sy7636a},
>> { .compatible = "maxim,max5970", .data = &maxim_max5970},
>> { .compatible = "maxim,max5978", .data = &maxim_max5970},
>> { .compatible = "maxim,max77705-battery", .data = &maxim_mon_max77705},
>> + { .compatible = "spacemit,p1", .data = &spacemit_p1, },
>> {}
>> };
>> MODULE_DEVICE_TABLE(of, simple_mfd_i2c_of_match);
>> --
>> 2.48.1
>>
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-08-25 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 2:45 [PATCH v12 0/7] spacemit: introduce P1 PMIC support Alex Elder
2025-08-13 2:45 ` [PATCH v12 1/7] dt-bindings: mfd: add support the SpacemiT P1 PMIC Alex Elder
2025-08-13 12:19 ` Troy Mitchell
2025-08-13 12:36 ` Alex Elder
2025-08-13 2:45 ` [PATCH v12 2/7] mfd: simple-mfd-i2c: add SpacemiT P1 support Alex Elder
2025-08-15 2:28 ` Troy Mitchell
2025-08-25 16:08 ` Alex Elder [this message]
2025-08-26 1:04 ` Troy Mitchell
2025-08-27 9:33 ` Troy Mitchell
2025-08-13 2:45 ` [PATCH v12 3/7] regulator: spacemit: support SpacemiT P1 regulators Alex Elder
2025-08-13 2:45 ` [PATCH v12 4/7] rtc: spacemit: support the SpacemiT P1 RTC Alex Elder
2025-08-13 2:45 ` [PATCH v12 5/7] riscv: dts: spacemit: enable the i2c8 adapter Alex Elder
2025-08-13 2:45 ` [PATCH v12 6/7] riscv: dts: spacemit: define fixed regulators Alex Elder
2025-08-13 2:45 ` [PATCH v12 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=b387ebdd-ae5d-4711-9e10-c61cb06f4b5b@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=guodong@riscstar.com \
--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=linux.amoon@gmail.com \
--cc=mat.jonczyk@o2.pl \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--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
all inboxes | Powered by JetHome®