From: Elliot Berman <quic_eberman@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Maulik Shah <quic_mkshah@quicinc.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_collinsd@quicinc.com>, <quic_lsrao@quicinc.com>,
<stable@vger.kernel.org>
Subject: Re: Re: [PATCH v4] soc: qcom: rpmh-rsc: Enhance check for VRM in-flight request
Date: Mon, 18 Mar 2024 14:22:14 -0700 [thread overview]
Message-ID: <20240318142037265-0700.eberman@hu-eberman-lv.qualcomm.com> (raw)
In-Reply-To: <vuyzqntyhzz5at5q7rxkix6ogavow4kltge26q62ihzhsblsuv@o43un23zaf4w>
On Sun, Mar 17, 2024 at 10:18:25PM -0500, Bjorn Andersson wrote:
> On Thu, Feb 15, 2024 at 10:55:44AM +0530, Maulik Shah wrote:
> > Each RPMh VRM accelerator resource has 3 or 4 contiguous 4-byte aligned
> > addresses associated with it. These control voltage, enable state, mode,
> > and in legacy targets, voltage headroom. The current in-flight request
> > checking logic looks for exact address matches. Requests for different
> > addresses of the same RPMh resource as thus not detected as in-flight.
> >
> > Add new cmd-db API cmd_db_match_resource_addr() to enhance the in-flight
> > request check for VRM requests by ignoring the address offset.
> >
> > This ensures that only one request is allowed to be in-flight for a given
> > VRM resource. This is needed to avoid scenarios where request commands are
> > carried out by RPMh hardware out-of-order leading to LDO regulator
> > over-current protection triggering.
> >
> > Fixes: 658628e7ef78 ("drivers: qcom: rpmh-rsc: add RPMH controller for QCOM SoCs")
> > cc: stable@vger.kernel.org
> > Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> > Tested-by: Elliot Berman <quic_eberman@quicinc.com> # sm8650-qrd
> > Signed-off-by: Maulik Shah <quic_mkshah@quicinc.com>
> > ---
> > Changes in v4:
> > - Simplify cmd_db_match_resource_addr()
> > - Remove unrelated changes to newly added logic
> > - Update function description comments
>
> You changed things, but retained Konrad's Reviewed-by...
>
> > - Replace Signed-off-by: with Tested-by: from Elliot
>
> Did Elliot test v4, or did you just translate his incorrect(?) s-o-b
> from v1 into a tested-by?
>
> We're about to write into the git history that Elliot says this version
> is tested to the best of his abilities...
>
No, I asked for it:
https://lore.kernel.org/all/20240214105605460-0800.eberman@hu-eberman-lv.qualcomm.com/
next prev parent reply other threads:[~2024-03-18 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 5:25 [PATCH v4] soc: qcom: rpmh-rsc: Enhance check for VRM in-flight request Maulik Shah
2024-03-18 3:18 ` Bjorn Andersson
2024-03-18 21:22 ` Elliot Berman [this message]
2024-04-21 22:29 ` Bjorn Andersson
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=20240318142037265-0700.eberman@hu-eberman-lv.qualcomm.com \
--to=quic_eberman@quicinc.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_collinsd@quicinc.com \
--cc=quic_lsrao@quicinc.com \
--cc=quic_mkshah@quicinc.com \
--cc=stable@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