From: James Calligeros <jcalligeros99@gmail.com>
To: viresh.kumar@linaro.org
Cc: jcalligeros99@gmail.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, nm@ti.com, rafael@kernel.org,
sboyd@kernel.org, vincent.guittot@linaro.org, vireshk@kernel.org
Subject: Re: [PATCH V2 5/5] OPP: decouple dt properties in opp_parse_supplies()
Date: Thu, 3 Nov 2022 22:24:25 +1000 [thread overview]
Message-ID: <3519763.iIbC2pHGDl@makoto> (raw)
In-Reply-To: <5acd93462bff6c108d65802fd39f6002dfadd1a0.1667473008.git.viresh.kumar@linaro.org>
On Thursday, 3 November 2022 9:01:08 PM AEST Viresh Kumar wrote:
> @@ -674,7 +677,7 @@ static int opp_parse_supplies(struct dev_pm_opp *opp, struct device *dev,
> bool triplet;
>
> microvolt = opp_parse_microvolt(opp, dev, opp_table, &triplet);
> - if (IS_ERR_OR_NULL(microvolt))
> + if (IS_ERR(microvolt))
> return PTR_ERR(microvolt);
Erroring out here will still block EM registration on platforms without
the opp-microvolt prop so we're back to square one, which means the
patch does not do what the description says it does. It behaves
almost identically to the current code.
I assume this is an intentional choice given the comments in
opp_parse_microvolt(), so the commit message should drop
references to fixing such platforms.
If this is a hard sticking point and opp_parse_supplies() must return
a regulator with opp-microvolt, then I am of the opinion that the parsing
of opp-microwatt should be detangled entirely from the regulator
infrastructure.
Otherwise for the whole series,
Tested-by: James Calligeros <jcalligeros99@gmail.com>
- James
next prev parent reply other threads:[~2022-11-03 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 11:01 [PATCH 0/5] OPP: Allow power/current values without voltage Viresh Kumar
2022-11-03 11:01 ` [PATCH 1/5] dt-bindings: opp: Fix usage of current in microwatt property Viresh Kumar
2022-11-03 11:01 ` [PATCH 2/5] dt-bindings: opp: Fix named " Viresh Kumar
2022-11-03 11:01 ` [PATCH 3/5] OPP: Parse named opp-microwatt property too Viresh Kumar
2022-11-03 11:01 ` [PATCH 4/5] OPP: Simplify opp_parse_supplies() by restructuring it Viresh Kumar
2022-11-03 11:01 ` [PATCH V2 5/5] OPP: decouple dt properties in opp_parse_supplies() Viresh Kumar
2022-11-03 12:24 ` James Calligeros [this message]
2022-11-03 13:10 ` Viresh Kumar
2022-11-03 15:23 ` James Calligeros
2022-11-04 5:07 ` Viresh Kumar
2022-11-04 5:25 ` James Calligeros
2022-11-04 5:28 ` Viresh Kumar
2022-11-04 5:08 ` Viresh Kumar
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=3519763.iIbC2pHGDl@makoto \
--to=jcalligeros99@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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