mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <quic_bjorande@quicinc.com>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: 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>, <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: Mon, 6 Nov 2023 15:01:03 -0800	[thread overview]
Message-ID: <20231106230103.GA3553829@hu-bjorande-lv.qualcomm.com> (raw)
In-Reply-To: <5e83d947-c77f-9318-4a4c-377a8304b8fd@quicinc.com>

On Mon, Nov 06, 2023 at 12:24:28PM +0530, Mukesh Ojha wrote:
> 
> 
> On 11/4/2023 1:03 AM, Bjorn Andersson wrote:
> > On Fri, Nov 03, 2023 at 04:27:12PM +0530, 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.
> > > 
> > 
> > As far as I can see, the only invocation of _qcom_llcc_cfg_program()
> > comes from qcom_llcc_cfg_program(), which is only called once, from
> > qcom_llcc_probe(), and here also seems to only be the single write to
> > these two registers.
> 
> It does not look to be single write but the write is for each slice
> in the same register which was overriding other slices values.
> 

Ahh, you're right. I missed that it was hitting the same register in
each iteration.

My concern remains though, unless a platform defines 32 slices only a
subset of the bits in the two registers will be touched - leaving the
remaining bits in whatever state they happened to have.

Regards,
Bjorn

> -Mukesh
> > 
> > This implies that "the previously configured bits" would be some unknown
> > configuration provided to us either from the bootloader or by reset of
> > the hardware. As such this changes the value of the two registers from
> > being known, to having 31 unknown bits.
> > 
> > 
> > I'm not saying that the change is wrong, but you're altering the
> > behavior of every platform except SDM845.
> > As such, I want the commit message to provide an actual problem
> > description, and mention the fact that you're changing the logic to
> > retain the state prior to Linux.
> > 
> > Regards,
> > Bjorn
> > 
> > > 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);
> > >   			if (ret)
> > >   				return ret;
> > >   		}
> > > --
> > > 2.25.1
> > > 

      parent reply	other threads:[~2023-11-06 23:01 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
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 [this message]

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=20231106230103.GA3553829@hu-bjorande-lv.qualcomm.com \
    --to=quic_bjorande@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=quic_mojha@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®