From: Mark Brown <broonie@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: Add TPS65185 driver
Date: Mon, 22 Dec 2025 12:36:02 +0000 [thread overview]
Message-ID: <84fdaf7c-4d4b-491f-975c-ebb14350fafd@sirena.org.uk> (raw)
In-Reply-To: <20251222-tps65185-submit-v1-2-34986b504d5f@kemnade.info>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
On Mon, Dec 22, 2025 at 01:18:31PM +0100, Andreas Kemnade wrote:
> Add a driver for the TPS65185 regulator. Implement handling of the various
> gpio pins. Because the PWRUP (=enable) pin functionality can be achieved
> by just using two bits instead, just ensure that it is set to a stable
> value.
The reason for having GPIO controlled enables on devices with register
maps is that it's generally substantially faster to update a GPIO than
to do I2C I/O.
> +static bool tps65185_volatile_reg(struct device *dev, unsigned int reg)
> +{
> + switch (reg) {
> + case TPS65185_REG_TMST_VALUE:
> + case TPS65185_REG_ENABLE:
Why is the enable register volatile? I can't see anything in the
datasheet that suggests that it should be.
> +static int tps65185_runtime_suspend(struct device *dev)
> +{
Implementing runtime suspend in a regulator is *very* non-idiomatic and
is leading to large amounts of open coding throughout the driver.
What's the story here? I'm very surprised that this wasn't in the
changelog.
+ if (data->wakeup_gpio) {
+ ret = gpiod_set_value_cansleep(data->wakeup_gpio, 0);
+ if (ret)
+ return ret;
+ }
This would usually be used for system suspend.
+ if (data->vin_reg) {
+ ret = regulator_disable(data->vin_reg);
+ if (ret)
+ goto reenable_wkup;
+ }
Can the device really operate without power?
> +static irqreturn_t tps65185_irq_thread(int irq, void *dev_id)
> +{
> + struct tps65185_data *data = dev_id;
> + unsigned int int_status_1, int_status_2;
> + int ret;
> +
> + /* read both status to have irq cleared */
> + regmap_read(data->regmap, TPS65185_REG_INT1, &int_status_1);
> +
> + ret = regmap_read(data->regmap, TPS65185_REG_INT2, &int_status_2);
> + if (!ret) {
> + if (int_status_2 & BIT(0))
> + complete(&data->tmst_completion);
> + }
> +
> + dev_dbg(data->dev, "irq status %02x %02x\n", int_status_1, int_status_2);
> +
> + return IRQ_HANDLED;
> +}
This unconditionally reports an interrupt even if none was detected.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-22 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 12:18 [PATCH 0/2] regulator: Add TPS65185 Andreas Kemnade
2025-12-22 12:18 ` [PATCH 1/2] dt-bindings: regulator: Add TI TPS65185 Andreas Kemnade
2025-12-22 12:36 ` Mark Brown
2025-12-22 12:18 ` [PATCH 2/2] regulator: Add TPS65185 driver Andreas Kemnade
2025-12-22 12:36 ` Mark Brown [this message]
2025-12-22 13:45 ` Andreas Kemnade
2025-12-22 15:07 ` Mark Brown
2025-12-24 8:12 ` Andreas Kemnade
2025-12-24 11:40 ` Mark Brown
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=84fdaf7c-4d4b-491f-975c-ebb14350fafd@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
/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®