From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, andersson@kernel.org,
agross@kernel.org, krzysztof.kozlowski@linaro.org
Cc: marijn.suijten@somainline.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: msm8998-yoshino: Use SONY GPIO names
Date: Tue, 3 Jan 2023 03:07:42 +0200 [thread overview]
Message-ID: <cf079fa7-56cf-2eea-993a-46c60adf5c49@linaro.org> (raw)
In-Reply-To: <20230102190157.970053-1-konrad.dybcio@linaro.org>
On 02/01/2023 21:01, Konrad Dybcio wrote:
> Sony ever so graciously provides GPIO line names in their downstream
> kernel (though sometimes they are not 100% accurate and you can judge
> that by simply looking at them and with what drivers they are used).
>
> Add these to the Yoshino devices DTs to better document the hardware and
> rename already-defined GPIO nodes to fit the "official" names.
> Note that 4k_ is replaced with four_k_ in one pin, as labels can't start
> with numbers.
>
> Lilac and Poplar have identical pin assignments.
>
> Diff between these two and maple:
>
> TLMM:
> - "NC",
> + "TS_VDDIO_EN",
>
> PMI8998:
> - "NC"
> + "USB_SWITCH_SEL"
>
> - "NC"
> + "4K_DISP_DCDC_EN"
>
> PM8005:
> - "NC"
> + "EAR_EN"
>
> Which is probably due to Maple being designed and released quite a bit
> earlier than the other two and it having a super high tech true-4K
> display.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> .../msm8998-sony-xperia-yoshino-maple.dts | 179 +++++++++++-
> .../dts/qcom/msm8998-sony-xperia-yoshino.dtsi | 260 +++++++++++++++---
The patch doesn't only add GPIO names, but also changes some labels and
node names. I can not judge whether they are correct changes or not, but
they definitely should be split out of the GPIO names patch.
> 2 files changed, 406 insertions(+), 33 deletions(-)
>
--
With best wishes
Dmitry
prev parent reply other threads:[~2023-01-03 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 19:01 Konrad Dybcio
2023-01-03 1:07 ` Dmitry Baryshkov [this message]
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=cf079fa7-56cf-2eea-993a-46c60adf5c49@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--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
all inboxes | Powered by JetHome®