From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexey Minnekhanov <alexeymin@postmarketos.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] ARM: dts: qcom: msm8974: switch TCSR mutex to MMIO
Date: Thu, 22 Sep 2022 08:44:57 +0200 [thread overview]
Message-ID: <e412810f-fd3e-1be9-3904-a684bfbeb9e2@linaro.org> (raw)
In-Reply-To: <37ebdd21-e46a-fac9-7e87-57042ab67d5c@postmarketos.org>
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
next prev parent reply other threads:[~2022-09-22 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 15:04 [PATCH v4 0/3] ARM/hwlock: qcom: switch TCSR mutex to MMIO (msm8974) Krzysztof Kozlowski
2022-09-20 15:04 ` [PATCH v4 1/3] dt-bindings: hwlock: qcom-hwspinlock: add syscon to MSM8974 Krzysztof Kozlowski
2022-09-26 19:49 ` Rob Herring
2022-09-20 15:04 ` [PATCH v4 2/3] ARM: dts: qcom: msm8974: add missing TCSR syscon compatible Krzysztof Kozlowski
2022-09-27 8:09 ` Neil Armstrong
2022-09-20 15:04 ` [PATCH v4 3/3] ARM: dts: qcom: msm8974: switch TCSR mutex to MMIO Krzysztof Kozlowski
2022-09-21 20:55 ` Alexey Minnekhanov
2022-09-22 6:44 ` Krzysztof Kozlowski [this message]
2022-09-21 19:09 ` [PATCH v4 0/3] ARM/hwlock: qcom: switch TCSR mutex to MMIO (msm8974) Luca Weiss
2022-09-21 19:18 ` Krzysztof Kozlowski
2022-10-18 3:05 ` (subset) " Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e412810f-fd3e-1be9-3904-a684bfbeb9e2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=alexeymin@postmarketos.org \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).