From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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
Subject: Re: [PATCH 4/5] arm64: dts: qcom: sm8550: Drop redundant VSYNC pin state
Date: Thu, 19 Feb 2026 10:19:57 +0100 [thread overview]
Message-ID: <c50de0e8-282e-4e1d-a8de-10dd047b9c30@oss.qualcomm.com> (raw)
In-Reply-To: <20260218-qcom-dts-redundant-pins-v1-4-2799b8a4184e@oss.qualcomm.com>
On 2/18/26 6:24 PM, Krzysztof Kozlowski wrote:
> The active and suspend pin state of VSYNC is exactly the same, so just
> use one node for both states.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-02-19 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 17:24 [PATCH 0/5] arm64: dts: qcom: Drop redundant VSYNC pin state Krzysztof Kozlowski
2026-02-18 17:24 ` [PATCH 1/5] arm64: dts: qcom: msm8996: " Krzysztof Kozlowski
2026-02-19 6:49 ` Dmitry Baryshkov
2026-02-19 7:23 ` Krzysztof Kozlowski
2026-02-19 7:46 ` Dmitry Baryshkov
2026-02-19 9:18 ` Konrad Dybcio
2026-02-18 17:24 ` [PATCH 2/5] arm64: dts: qcom: msm8998: " Krzysztof Kozlowski
2026-02-19 6:51 ` Dmitry Baryshkov
2026-02-19 8:40 ` Dmitry Baryshkov
2026-02-19 9:19 ` Konrad Dybcio
2026-02-18 17:24 ` [PATCH 3/5] arm64: dts: qcom: sdm845-axolotl: " Krzysztof Kozlowski
2026-02-19 6:52 ` Dmitry Baryshkov
2026-02-19 9:19 ` Konrad Dybcio
2026-02-18 17:24 ` [PATCH 4/5] arm64: dts: qcom: sm8550: " Krzysztof Kozlowski
2026-02-19 6:57 ` Dmitry Baryshkov
2026-02-19 9:19 ` Konrad Dybcio [this message]
2026-02-18 17:24 ` [PATCH 5/5] arm64: dts: qcom: sm8650: " Krzysztof Kozlowski
2026-02-19 6:58 ` Dmitry Baryshkov
2026-02-19 9:20 ` Konrad Dybcio
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=c50de0e8-282e-4e1d-a8de-10dd047b9c30@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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