[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9492bc16-2d8f-44a1-b2d6-d5f8353f30fa@linaro.org>
Date: Mon, 4 Sep 2023 17:58:06 +0200
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Vignesh Viswanathan <quic_viswanat@...cinc.com>, agross@...nel.org,
andersson@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, ohad@...ery.com,
baolin.wang@...ux.alibaba.com, linux-remoteproc@...r.kernel.org
Cc: quic_kathirav@...cinc.com, quic_anusha@...cinc.com,
quic_sjaganat@...cinc.com, quic_srichara@...cinc.com,
quic_varada@...cinc.com
Subject: Re: [PATCH 0/3] Fix tcsr_mutex register for IPQ6018
On 4.09.2023 07:50, Vignesh Viswanathan wrote:
> IPQ6018 has 32 tcsr_mutext hwlock registers of 0x1000 size each.
> The compatible string qcom,ipq6018-tcsr-mutex is mapped to
> of_msm8226_tcsr_mutex which has 32 locks configured with stride of 0x80
> and doesn't match the HW present in IPQ6018.
>
> This series fixes the following:
> 1. Fix the tcsr_mutex hwlock register size to 0x20000 in ipq6018.dtsi.
> 2. Remove qcom,ipq6018-tcsr-mutex compatible string for tcsr_mutex in
> ipq6018.dtsi.
> 3. Drop unused qcom,ipq6018-tcsr-mutex compatible string from
> qcom_hwspinlock driver and dt-bindings.
>
Sounds like 20230904063344.4144086-1-quic_viswanat@...cinc.com can't
go in without this then?
Konrad
Powered by blists - more mailing lists