From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Atul Dhudase <quic_adhudase@quicinc.com>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<swboyd@chromium.org>, <isaacm@codeaurora.org>,
<dianders@chromium.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc: qcom: llcc: Fix dis_cap_alloc and retain_on_pc configuration
Date: Fri, 3 Nov 2023 16:47:51 +0530 [thread overview]
Message-ID: <c5eb223b-b7b1-c85f-a0d5-ab3cc3e86efa@quicinc.com> (raw)
In-Reply-To: <20231103105712.1159213-1-quic_adhudase@quicinc.com>
On 11/3/2023 4:27 PM, Atul Dhudase wrote:
> While programming dis_cap_alloc and retain_on_pc, set a bit
> corresponding to a specific SCID without disturbing the
> previously configured bits.
>
> Fixes: c14e64b46944 ("soc: qcom: llcc: Support chipsets that can write to llcc")
> Signed-off-by: Atul Dhudase <quic_adhudase@quicinc.com>
> ---
> drivers/soc/qcom/llcc-qcom.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/soc/qcom/llcc-qcom.c b/drivers/soc/qcom/llcc-qcom.c
> index 674abd0d6700..509d972c1bd9 100644
> --- a/drivers/soc/qcom/llcc-qcom.c
> +++ b/drivers/soc/qcom/llcc-qcom.c
> @@ -941,15 +941,15 @@ static int _qcom_llcc_cfg_program(const struct llcc_slice_config *config,
> u32 disable_cap_alloc, retain_pc;
>
> disable_cap_alloc = config->dis_cap_alloc << config->slice_id;
> - ret = regmap_write(drv_data->bcast_regmap,
> - LLCC_TRP_SCID_DIS_CAP_ALLOC, disable_cap_alloc);
> + ret = regmap_update_bits(drv_data->bcast_regmap, LLCC_TRP_SCID_DIS_CAP_ALLOC,
> + BIT(config->slice_id), disable_cap_alloc);
> if (ret)
> return ret;
>
> if (drv_data->version < LLCC_VERSION_4_1_0_0) {
> retain_pc = config->retain_on_pc << config->slice_id;
> - ret = regmap_write(drv_data->bcast_regmap,
> - LLCC_TRP_PCB_ACT, retain_pc);
> + ret = regmap_update_bits(drv_data->bcast_regmap, LLCC_TRP_PCB_ACT,
> + BIT(config->slice_id), retain_pc);
Good catch, LGTM
Thanks
-Mukesh
> if (ret)
> return ret;
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-11-03 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 10:57 Atul Dhudase
2023-11-03 11:17 ` Mukesh Ojha [this message]
2023-11-03 15:30 ` Mukesh Ojha
2023-11-03 14:48 ` Doug Anderson
2023-11-03 19:33 ` Bjorn Andersson
2023-11-06 6:54 ` Mukesh Ojha
2023-11-06 21:55 ` Stephen Boyd
2023-11-07 13:16 ` Mukesh Ojha
2023-11-07 15:27 ` Atul Dhudase (QUIC)
2023-11-09 20:34 ` Stephen Boyd
2023-12-05 22:04 ` Doug Anderson
2023-12-06 10:38 ` Mukesh Ojha
2023-11-06 23:01 ` 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=c5eb223b-b7b1-c85f-a0d5-ab3cc3e86efa@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=isaacm@codeaurora.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_adhudase@quicinc.com \
--cc=swboyd@chromium.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®