From: Elliot Berman <quic_eberman@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Gabor Juhos <j4g8y7@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: Re: [PATCH] firmware: qcom_scm: disable clocks if qcom_scm_bw_enable() fails
Date: Tue, 5 Mar 2024 20:10:55 -0800 [thread overview]
Message-ID: <20240305200306921-0800.eberman@hu-eberman-lv.qualcomm.com> (raw)
In-Reply-To: <d655a4db-89a8-4b03-86b1-55258d37aa19@linaro.org>
On Tue, Mar 05, 2024 at 10:15:19PM +0100, Konrad Dybcio wrote:
>
>
> On 3/4/24 14:14, Gabor Juhos wrote:
> > There are several functions which are calling qcom_scm_bw_enable()
> > then returns immediately if the call fails and leaves the clocks
> > enabled.
> >
> > Change the code of these functions to disable clocks when the
> > qcom_scm_bw_enable() call fails. This also fixes a possible dma
> > buffer leak in the qcom_scm_pas_init_image() function.
> >
> > Compile tested only due to lack of hardware with interconnect
> > support.
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 65b7ebda5028 ("firmware: qcom_scm: Add bw voting support to the SCM interface")
> > Signed-off-by: Gabor Juhos <j4g8y7@gmail.com>
> > ---
>
> Taking a closer look, is there any argument against simply
> putting the clk/bw en/dis calls in qcom_scm_call()?
We shouldn't do this because the clk/bw en/dis calls are only needed in
few SCM calls.
Thanks,
Elliot
next prev parent reply other threads:[~2024-03-06 4:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:14 Gabor Juhos
2024-03-04 16:20 ` Mukesh Ojha
2024-03-05 21:15 ` Konrad Dybcio
2024-03-06 4:10 ` Elliot Berman [this message]
2024-03-06 16:02 ` Konrad Dybcio
2024-03-06 18:01 ` Elliot Berman
2024-03-06 18:03 ` Gabor Juhos
2024-03-16 17:58 ` Bjorn Andersson
2024-03-17 16:27 ` 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=20240305200306921-0800.eberman@hu-eberman-lv.qualcomm.com \
--to=quic_eberman@quicinc.com \
--cc=andersson@kernel.org \
--cc=j4g8y7@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_sibis@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
all inboxes | Powered by JetHome®