linux-kernel - Re: [PATCH] arm64: dts: qcom: qcm6490-idp: Update protected clocks list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0ab2552a-3b8d-4b4f-8f9e-8b0c4f5bf6ea@quicinc.com>
Date: Thu, 27 Feb 2025 09:56:27 +0530
From: Taniya Das <quic_tdas@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC: Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio
	<konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski
	<krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Ajit Pandey
	<quic_ajipan@...cinc.com>,
        Imran Shaik <quic_imrashai@...cinc.com>,
        "Jagadeesh Kona" <quic_jkona@...cinc.com>,
        <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: qcm6490-idp: Update protected clocks
 list



On 2/27/2025 9:50 AM, Dmitry Baryshkov wrote:
> On Thu, Feb 27, 2025 at 09:42:39AM +0530, Taniya Das wrote:
>>
>>
>> On 2/26/2025 10:12 AM, Bjorn Andersson wrote:
>>> On Thu, Feb 06, 2025 at 03:43:21PM +0530, Taniya Das wrote:
>>>> Certain clocks are not accessible on QCM6490-IDP board,
>>>> thus mark them as protected.
>>>>
>>>> Signed-off-by: Taniya Das <quic_tdas@...cinc.com>
>>>> ---
>>>> Mark few clocks as protected on IDP of QCM6490.
>>>>
>>>> This patchset is separated out from the series[1] to remove dependency from
>>>> the LPASS reset.
>>>> [1]: https://lore.kernel.org/all/20240816-qcm6490-lpass-reset-v1-0-a11f33cad3c5@quicinc.com/
>>>> ---
>>>>  arch/arm64/boot/dts/qcom/qcm6490-idp.dts | 21 +++++++++++++++++++++
>>>
>>> I merged the patch adding this board in November 2023, are you saying
>>> that for the last 15 months no one has actually booted it!?
>>>
>>
>> I am not sure, I had got request to help boot the board which was not
>> due to these clocks.
> 
> So, was the original submission in November 2023 broken or was it broken
> by a later firmware upgrade which started to protect those clocks?
> 
That's a fair question, probably the later broke it.