From: Matthias Kaehlcke <mka@chromium.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Brian Norris <briannorris@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] regulator: core: Limit propagation of parent voltage count and list
Date: Mon, 27 Mar 2017 10:39:02 -0700 [thread overview]
Message-ID: <20170327173902.GB84219@google.com> (raw)
In-Reply-To: <f38f79fb-71df-7ce0-86b9-ff6d2d0d4470@osg.samsung.com>
Thanks for the reviews and testing!
El Sat, Mar 25, 2017 at 02:05:47AM -0300 Javier Martinez Canillas ha dit:
On 03/24/2017 05:38 PM, Brian Norris wrote:
> > On Fri, Mar 24, 2017 at 01:09:52PM -0700, Matthias Kaehlcke wrote:
> >> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> >> index 53d4fc70dbd0..121838e0125b 100644
> >> --- a/drivers/regulator/core.c
> >> +++ b/drivers/regulator/core.c
> >> @@ -2487,6 +2487,10 @@ static int _regulator_list_voltage(struct regulator *regulator,
> >> if (lock)
> >> mutex_unlock(&rdev->mutex);
> >> } else if (rdev->supply) {
> >> + // Limit propagation of parent values to switch regulators
> >
> > The kernel doesn't use C99 comments. Oddly enough, this isn't actually
>
> +1
Will fix
> > in the coding style doc (Documentation/process/coding-style.rst), nor is
> > it caught by scripts/checkpatch.pl (even though it clearly has a 'C99
> > comment' rule).
> >
> >> + if (ops->get_voltage || ops->get_voltage_sel)
>
> It's valid to have a .get_voltage_sel callback without a .list_voltage?
>
> At least it seems that _regulator_get_voltage() assumes that having a
> .get_voltage_sel implies that a .list_voltage will also be available.
>
> static int _regulator_get_voltage(struct regulator_dev *rdev)
> {
> ...
> if (rdev->desc->ops->get_voltage_sel) {
> sel = rdev->desc->ops->get_voltage_sel(rdev);
> if (sel < 0)
> return sel;
> ret = rdev->desc->ops->list_voltage(rdev, sel);
> } else if (rdev->desc->ops->get_voltage) {
> ...
> }
The same function (from which I derived the conditions) suggests that
a regulator could have a .list_voltage op even if it doesn't have
.get_voltage_sel:
> ...
> if (rdev->desc->ops->get_voltage_sel) {
> ...
> } else if (rdev->desc->ops->get_voltage) {
> ...
> } else if (rdev->desc->ops->list_voltage) {
I don't know for sure if this condition is superfluous or if there are
cases where it makes sense to have a .list_voltage but not
.get_voltage_sel.
> I wonder if instead of always checking if the regulator lacks operations,
> it wouldn't be better to do it just once and store that the regulator is
> a switch so that state can be used as explicit check for switch instead.
>
> Something like if (!rdev->supply || !rdev->switch) looks more clear
> to me.
I agree and we can even reduce it to if (!rdev_switch) since a switch
implicitly has a supply.
I'll send out a new version soon.
Matthias
next prev parent reply other threads:[~2017-03-27 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 20:09 [PATCH] regulator: core: Limit propagation of parent voltage count and list Matthias Kaehlcke
2017-03-24 20:38 ` Brian Norris
2017-03-25 5:05 ` Javier Martinez Canillas
2017-03-27 10:21 ` Mark Brown
2017-03-27 17:39 ` Matthias Kaehlcke [this message]
2017-03-27 17:54 ` Javier Martinez Canillas
2017-03-27 18:13 ` Mark Brown
2017-03-27 18:20 ` Matthias Kaehlcke
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=20170327173902.GB84219@google.com \
--to=mka@chromium.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=javier@osg.samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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