From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Nikita Travkin <nikita@trvn.ru>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
"Adam Słaboń" <asaillen@protonmail.com>
Subject: Re: [PATCH 3/3] arm64: dts: qcom: msm8939-wingtech-wt82918: Add Lenovo Vibe K5 devices
Date: Fri, 12 Jul 2024 21:54:09 +0200 [thread overview]
Message-ID: <a05951f8-792d-4c83-802b-0350dd8760cb@linaro.org> (raw)
In-Reply-To: <2146ca56-6c2c-48a3-8e77-75aa04cb2b4c@linaro.org>
On 12.07.2024 9:53 PM, Konrad Dybcio wrote:
> On 12.07.2024 6:04 PM, Nikita Travkin wrote:
[...]
>> +&pm8916_mpps {
>> + pwm_out: mpp4-state {
>> + pins = "mpp4";
>> + function = "digital";
>> + power-source = <PM8916_MPP_VPH>;
>> + output-low;
>> + qcom,dtest = <1>;
>
> I think you meant qcom,dtest-output
No, I apparently found this in msm-3.10, ignore this comment
Konrad
next prev parent reply other threads:[~2024-07-12 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 16:04 [PATCH 0/3] Introduce msm8916/39 based Lenovo devices Nikita Travkin
2024-07-12 16:04 ` [PATCH 1/3] dt-bindings: arm: qcom: Add " Nikita Travkin
2024-07-13 10:00 ` Krzysztof Kozlowski
2024-07-12 16:04 ` [PATCH 2/3] arm64: dts: qcom: msm8916-wingtech-wt865x8: Add Lenovo A6000/A6010 Nikita Travkin
2024-07-12 16:04 ` [PATCH 3/3] arm64: dts: qcom: msm8939-wingtech-wt82918: Add Lenovo Vibe K5 devices Nikita Travkin
2024-07-12 19:53 ` Konrad Dybcio
2024-07-12 19:54 ` Konrad Dybcio [this message]
2024-07-13 10:41 ` Nikita Travkin
2024-07-13 10:02 ` Krzysztof Kozlowski
2024-07-13 10:37 ` Nikita Travkin
2024-07-13 11:07 ` Nikita Travkin
2024-07-13 16:12 ` Dmitry Baryshkov
2024-07-13 16:26 ` Nikita Travkin
2024-07-15 12:12 ` [PATCH 0/3] Introduce msm8916/39 based Lenovo devices Rob Herring (Arm)
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=a05951f8-792d-4c83-802b-0350dd8760cb@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=asaillen@protonmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).