From: Mark Brown <broonie@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v2 0/2] regulator_sync_state() support
Date: Fri, 29 May 2020 14:09:17 +0100 [thread overview]
Message-ID: <20200529130917.GM4610@sirena.org.uk> (raw)
In-Reply-To: <20200528190610.179984-1-saravanak@google.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Thu, May 28, 2020 at 12:06:08PM -0700, Saravana Kannan wrote:
> The simplified explanation of the problem is, for regulators left on by
> the bootloader, we want to keep them on until all the consumers are
> probed. This is because we need to protect consumer-A from turning off a
> shared regulator used by consumer-B. Once consumer-B (and all the other
> consumers come up), they can do it themselves and the regulator
> framework no longer needs to keep the regulator on.
> So, this is not just about module or device probe ordering between
> suppliers and consumers. Even if we get the probe order prefectly right,
> it still won't solve this problem.
This logic seems to be circular - can you be concrete please?
> We can eventually extend this to also cover voltage and other
> properties, but in this patch series I want to get this right for
> "enabled/disabled" first.
I'm quite worried about the extension to voltage changes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-05-29 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 19:06 Saravana Kannan
2020-05-28 19:06 ` [PATCH v2 1/2] driver core: Add dev_set_drv_sync_state() Saravana Kannan
2020-05-28 19:06 ` [PATCH v2 2/2] regulator: Add support for sync_state() callbacks Saravana Kannan
2020-05-29 13:00 ` Mark Brown
2020-05-30 2:39 ` Saravana Kannan
2020-06-01 17:23 ` Mark Brown
2020-06-09 3:16 ` Saravana Kannan
2020-06-09 10:51 ` Mark Brown
2020-06-15 10:27 ` Ulf Hansson
2020-06-15 11:49 ` Mark Brown
2020-06-15 15:37 ` Ulf Hansson
2020-05-29 13:09 ` Mark Brown [this message]
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=20200529130917.GM4610@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.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
Powered by JetHome