[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e412810f-fd3e-1be9-3904-a684bfbeb9e2@linaro.org>
Date: Thu, 22 Sep 2022 08:44:57 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Alexey Minnekhanov <alexeymin@...tmarketos.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Ohad Ben-Cohen <ohad@...ery.com>,
Baolin Wang <baolin.wang@...ux.alibaba.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-remoteproc@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/3] ARM: dts: qcom: msm8974: switch TCSR mutex to MMIO
On 21/09/2022 22:55, Alexey Minnekhanov wrote:
> Hi,
>
> On 20.09.2022 18:04, Krzysztof Kozlowski wrote:
>
>> - tcsr_mutex: tcsr-mutex {
>> - compatible = "qcom,tcsr-mutex";
>> - syscon = <&tcsr_mutex_block 0 0x80>;
>
> I'm looking and don't understand where does this information go, is it
> lost in the conversion? I mean those "0 0x80" parameters to syscon
> reference.
This compatible is using:
of_msm8226_tcsr_mutex
.stride = 0x80,
Best regards,
Krzysztof
Powered by blists - more mailing lists