From: Krzysztof Kozlowski <krzk@kernel.org>
To: yedaya.ka@gmail.com, "Kamil Gołda" <kamil.golda@protonmail.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 3/3] arm64: dts: qcom: sm6125-xiaomi-laurel-sprout: Add Focaltech FT3518 touchscreen
Date: Tue, 20 Jan 2026 08:13:42 +0100 [thread overview]
Message-ID: <8b6015a7-ede6-4b4c-9fce-d979865db308@kernel.org> (raw)
In-Reply-To: <20260118-touchscreen-patches-v3-3-1c6a729c5eb4@gmail.com>
On 18/01/2026 21:29, Yedaya Katsman via B4 Relay wrote:
> +
> &rpm_requests {
> regulators-0 {
> compatible = "qcom,rpm-pm6125-regulators";
> @@ -387,6 +425,81 @@ &sdhc_2 {
>
> &tlmm {
> gpio-reserved-ranges = <22 2>, <28 6>;
> +
> + pmx_ts_reset_active {
You must follow DTS coding style. Do not copy here code from downstream,
ever.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-20 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 20:29 [PATCH v3 0/3] Support FT3518 touchscreen in xiaomi-laurel Yedaya Katsman via B4 Relay
2026-01-18 20:29 ` [PATCH v3 1/3] dt-bindings: input: touchscreen: edt-ft5x06: Add FocalTech FT3518 Yedaya Katsman via B4 Relay
2026-01-20 19:53 ` Dmitry Torokhov
2026-01-18 20:29 ` [PATCH v3 2/3] drivers: " Yedaya Katsman via B4 Relay
2026-01-20 19:53 ` Dmitry Torokhov
2026-01-18 20:29 ` [PATCH v3 3/3] arm64: dts: qcom: sm6125-xiaomi-laurel-sprout: Add Focaltech FT3518 touchscreen Yedaya Katsman via B4 Relay
2026-01-20 7:13 ` Krzysztof Kozlowski [this message]
2026-01-20 12:43 ` Konrad Dybcio
2026-01-20 1:57 ` [PATCH v3 0/3] Support FT3518 touchscreen in xiaomi-laurel Rob Herring
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=8b6015a7-ede6-4b4c-9fce-d979865db308@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kamil.golda@protonmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=yedaya.ka@gmail.com \
/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