Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
Message-ID: <0d66efa6-7697-9314-b649-22cdc4d8fa59@quicinc.com>
Date:   Wed, 6 Dec 2023 16:08:43 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: [PATCH] soc: qcom: llcc: Fix dis_cap_alloc and retain_on_pc
 configuration
Content-Language: en-US
To:     Doug Anderson <dianders@chromium.org>,
        Stephen Boyd <swboyd@chromium.org>
CC:     Atul Dhudase <quic_adhudase@quicinc.com>,
        Bjorn Andersson <quic_bjorande@quicinc.com>,
        "agross@kernel.org" <agross@kernel.org>,
        "andersson@kernel.org" <andersson@kernel.org>,
        "konrad.dybcio@linaro.org" <konrad.dybcio@linaro.org>,
        "isaacm@codeaurora.org" <isaacm@codeaurora.org>,
        "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
References: <20231103105712.1159213-1-quic_adhudase@quicinc.com>
 <20231103193345.GY3553829@hu-bjorande-lv.qualcomm.com>
 <5e83d947-c77f-9318-4a4c-377a8304b8fd@quicinc.com>
 <CAE-0n50HwE+gNYotYXduer3b=O+c3ZWLC_8gEmpo0KQmtzmNvQ@mail.gmail.com>
 <d1e3adb5-b179-a119-fc0c-f92c2b84c7c2@quicinc.com>
 <SN4PR0201MB8806AF236D696E15CDC6400CF9A9A@SN4PR0201MB8806.namprd02.prod.outlook.com>
 <CAE-0n50kf82BLXPAAUN+kba9osA-gEetm96tS7aRVzUUNHbCgQ@mail.gmail.com>
 <CAD=FV=W7pjg=vfrkZg4i=YaKpoNT+_hX_3tgDz8VQiH+OquOTQ@mail.gmail.com>
From:   Mukesh Ojha <quic_mojha@quicinc.com>
In-Reply-To: <CAD=FV=W7pjg=vfrkZg4i=YaKpoNT+_hX_3tgDz8VQiH+OquOTQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk


On 12/6/2023 3:34 AM, Doug Anderson wrote:
> Hi,
> 
> On Thu, Nov 9, 2023 at 12:34 PM Stephen Boyd <swboyd@chromium.org> wrote:
>>
>> Quoting Atul Dhudase (QUIC) (2023-11-07 07:27:54)
>>> Hi,
>>>
>>> On 11/7/2023 6:46 PM, Mukesh Ojha wrote:
>>>> On 11/7/2023 3:25 AM, Stephen Boyd wrote:
>>>>> Quoting Mukesh Ojha (2023-11-05 22:54:28)
>>>>>>
>>>>>>
>>>>>> 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.
>>>>>
>>>>> Can you add that detail to the commit text? What's the seriousness
>>>>> of the issue? Why should it be backported to stable? Is something
>>>>> seriously broken because a slice configuration is overwritten? Does
>>>>> it mean that some allocation made in a slice is being lost over
>>>>> power collapse (pc) when it shouldn't be?
>>>>
>>>> @Atul will update the commit text as per suggestion.
>>>>
>>>> And yes, without this change, retention feature will not work properly.
>>>>
>>>> -Mukesh
>>>
>>> Does this commit text make sense? If so, I will update patch accordingly.
>>>
>>> When configuring capacity based allocation and power collapse retention, writing to the same register for each slice caused overwriting of the values for other slices, leading to misconfiguration for majority of the slices.
>>> To address this, only modify the bits associated with each slice while retaining the values of the remaining bits, as they were prior to the Linux configuration.
>>
>> This commit text doesn't say what, if anything, is broken. Does it save
>> power when it didn't before? Why is it critical to backport this to
>> stable kernels? Was the driver overwriting other bits in this register
>> that were critical to power, performance, or correctness? Or was
>> everything working out because the last slice to be written was the only
>> important one?
> 
> Whatever happened to this patch? It seemed like it might be important
> and it never landed. I guess the only thing that was blocking it from
> landing was some commit text that explained _why_ it was important and
> that never got written.
> 
> I guess Bjorn was also worried that any bits that weren't updated by
> the kernel would now be left in their default state (however the
> bootloader left them). It would be good to indicate in the commit text
> if that matters and what is in those other bits.

Let me add that.
Completely missed to track this change., Thanks for reminding..

-Mukesh

> 
> 
> -Doug