From: Mark Brown <broonie@kernel.org>
To: Tapio Reijonen <tapio.reijonen@vaisala.com>
Cc: Saravanan Sekar <sravanhome@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] regulator: Add MPS MPQ4210 buck-boost regulator support
Date: Thu, 10 Sep 2026 16:58:29 +0100 [thread overview]
Message-ID: <cd0d2e42-5fbe-4cf9-81a7-cb102f543e67@sirena.org.uk> (raw)
In-Reply-To: <20260910-mpq4210-regulator-v1-0-d37e208dfc8d@vaisala.com>
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
On Thu, Sep 10, 2026 at 08:51:40AM +0000, Tapio Reijonen wrote:
> One consequence of the hardware worth spelling out: the MPQ4210 does not
> respond on the I2C bus while EN is deasserted. The enable GPIO is
> therefore claimed and asserted before the first register access and held
> for the lifetime of the device, rather than being handed to the core as
> regulator_config::ena_gpiod, which would drop the bus along with the
> output.
This is what regmap's cache only mode is for.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-10 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 8:51 [PATCH 0/2] regulator: Add MPS MPQ4210 buck-boost regulator support Tapio Reijonen
2026-09-10 8:51 ` [PATCH 1/2] regulator: dt-bindings: Add MPS MPQ4210 Tapio Reijonen
2026-09-10 9:01 ` sashiko-bot
2026-09-11 8:45 ` Krzysztof Kozlowski
2026-09-10 8:51 ` [PATCH 2/2] regulator: Add MPS MPQ4210 buck-boost regulator driver Tapio Reijonen
2026-09-11 18:48 ` Uwe Kleine-König
2026-09-10 15:58 ` Mark Brown [this message]
2026-09-10 15:58 ` [PATCH 0/2] regulator: Add MPS MPQ4210 buck-boost regulator support 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=cd0d2e42-5fbe-4cf9-81a7-cb102f543e67@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sravanhome@gmail.com \
--cc=tapio.reijonen@vaisala.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