From: Mark Brown <broonie@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1] regulator: Don't error out fixed regulator in regulator_sync_voltage()
Date: Thu, 21 Oct 2021 14:12:00 +0100 [thread overview]
Message-ID: <YXFnIPXwPuNWM4XG@sirena.org.uk> (raw)
In-Reply-To: <20211021110707.20416-1-digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Thu, Oct 21, 2021 at 02:07:07PM +0300, Dmitry Osipenko wrote:
> Fixed regulator can't change voltage and regulator_sync_voltage() returns
> -EINVAL in this case. Make regulator_sync_voltage() to succeed for a fixed
> regulator.
> +++ b/drivers/regulator/core.c
> @@ -4249,6 +4249,9 @@ int regulator_sync_voltage(struct regulator *regulator)
> struct regulator_voltage *voltage = ®ulator->voltage[PM_SUSPEND_ON];
> int ret, min_uV, max_uV;
>
> + if (rdev->desc->fixed_uV && rdev->desc->n_voltages == 1)
> + return 0;
> +
> regulator_lock(rdev);
It's unclear why this is checking both fixed_uV and n_voltages. TBH
this feels like a higher level issue - with normal voltage configuration
we would have noticed that our constraints prevent the voltage changing
and not go as far as trying to actually apply a new configuration. I
would expect a similar thing to be happening here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-21 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 11:07 [PATCH v1] regulator: Don't error out fixed regulator in regulator_sync_voltage() Dmitry Osipenko
2021-10-21 13:12 ` Mark Brown [this message]
2021-10-21 13:46 ` Dmitry Osipenko
2021-10-21 13:55 ` Dmitry Osipenko
2021-10-21 14:33 ` 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=YXFnIPXwPuNWM4XG@sirena.org.uk \
--to=broonie@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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