[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17c8ba39-2bcf-5799-13ff-bb96249dbf61@linaro.org>
Date: Mon, 4 Sep 2023 08:42:09 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Vignesh Viswanathan <quic_viswanat@...cinc.com>, agross@...nel.org,
andersson@...nel.org, konrad.dybcio@...aro.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 2/3] hwspinlock: qcom: Drop unused qcom,ipq6018-tcsr-mutex
On 04/09/2023 07:50, Vignesh Viswanathan wrote:
> qcom,ipq6018-tcsr-mutex maps to incorrect config of IPQ6018 and is
> dropped from the devictree.
No, it is not dropped.
> IPQ6018 will use qcom,tcsr-mutex compatible
> string.
No, it will not.
>
> Drop qcom,ipq6018-tcsr-mutex compatible string from
> qcom_hwspinlock_of_match table.
Why? Do not write what you are doing here, but why you are doing it.
Best regards,
Krzysztof
Powered by blists - more mailing lists