From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Doug Anderson <dianders@chromium.org>,
Andrew Halaney <ahalaney@redhat.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Johan Hovold <johan@kernel.org>,
Johan Hovold <johan+kernel@kernel.org>
Subject: Re: [PATCH v3] regulator: dt-bindings: qcom,rpmh: Indicate regulator-allow-set-load dependencies
Date: Thu, 8 Sep 2022 16:48:59 +0200 [thread overview]
Message-ID: <ee6b8de0-4293-aa1b-4b38-e9c834e0251b@linaro.org> (raw)
In-Reply-To: <Yxn+eieg1Xr28rEk@sirena.org.uk>
On 08/09/2022 16:38, Mark Brown wrote:
> On Thu, Sep 08, 2022 at 04:29:29PM +0200, Krzysztof Kozlowski wrote:
>
>> Sorry, I don't find it related. Whether RPM has modes or not, does not
>> matter to this discussion unless it sets as well allow-set-load without
>> the mode... and then how does it work? In current implementation it
>> shouldn't...
>
> It works perfectly fine, if the driver has a set_load() operation then
> we call that and don't do anything to do with modes.
Ah, I see now set_load() in drms_uA_update() in first if-arm. Makes
sense I guess.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-08 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 20:49 Andrew Halaney
2022-09-08 10:25 ` Krzysztof Kozlowski
2022-09-08 14:23 ` Doug Anderson
2022-09-08 14:29 ` Krzysztof Kozlowski
2022-09-08 14:38 ` Doug Anderson
2022-09-08 14:49 ` Krzysztof Kozlowski
2022-09-08 14:38 ` Mark Brown
2022-09-08 14:48 ` Krzysztof Kozlowski [this message]
2022-09-08 14:50 ` Andrew Halaney
2022-09-08 14:53 ` Andrew Halaney
2022-09-08 15:50 ` Mark Brown
2022-12-28 10:37 ` Krzysztof Kozlowski
2022-12-28 10:58 ` Johan Hovold
2022-12-28 11:11 ` Krzysztof Kozlowski
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=ee6b8de0-4293-aa1b-4b38-e9c834e0251b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=johan+kernel@kernel.org \
--cc=johan@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®