From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Rob Clark <robdclark@chromium.org>,
Fritz Koenig <frkoenig@google.com>
Subject: Re: [RFT PATCH v2 2/2] arm64: dts: qcom: sdm845: align TLMM pin configuration with DT schema
Date: Fri, 2 Dec 2022 09:15:25 +0100 [thread overview]
Message-ID: <68bcdf25-e8e3-f817-f213-efb0bce3f43a@linaro.org> (raw)
In-Reply-To: <CAD=FV=XeaskcBRVRQDoha7Xiv9j57fuvtcSJUeN7HCZSGVJ8uQ@mail.gmail.com>
On 02/12/2022 01:50, Doug Anderson wrote:
> Hi,
>
> On Fri, Nov 18, 2022 at 8:42 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> DT schema expects TLMM pin configuration nodes to be named with
>> '-state' suffix and their optional children with '-pins' suffix.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
>>
>> Cc: Doug Anderson <dianders@chromium.org>
>>
>> Tested on Qualcomm RB3. Please kndly test a bit more on other devices.
>> This should not have an functional impact.
>
> Added Rob Clark and Fritz who are the only people I know that still do
> anything with cheza.
>
>
>> - wcd_intr_default: wcd_intr_default {
>> + wcd_intr_default: wcd-intr-default-state {
>> pins = <54>;
>
> Not new to your patch, but I'm surprised it truly works to use an
> integer for a pin? How does it know that 54 is an integer and not a
> string???
Maybe it passes the checks as phandle...
Anyway, I'll fix it in separate patch, assuming this is GPIO54. On
schematics I see CODEC_INT1_N GPIO_54.
>
>
>> &qup_uart3_default {
>> - pinmux {
>> - pins = "gpio41", "gpio42", "gpio43", "gpio44";
>> + cts-rts-pins {
>> + pins = "gpio41", "gpio42";
>> function = "qup3";
>> };
>> };
>
> FWIW, I would have expected that the SoC dtsi file would get a "4-pin"
> definition (similar to what you did with qup_uart6_4pin) and then we'd
> use that here.
Sure.
>
>
>> qup_uart6_4pin: qup-uart6-4pin-state {
>> -
>> - cts-pins {
>> + qup_uart6_4pin_cts: cts-pins {
>> pins = "gpio45";
>> function = "qup6";
>> - bias-pull-down;
>
> After your patch, where is the above bias set for cheza, db845c,
> oneplus, shift-axolotl, ...?
>
>
>> };
>>
>> - rts-tx-pins {
>> + qup_uart6_4pin_rts_tx: rts-tx-pins {
>> pins = "gpio46", "gpio47";
>> function = "qup6";
>> - drive-strength = <2>;
>> - bias-disable;
>
> After your patch, where is the above bias / drive-strength set?
They don't use 4-pin setup. If they use, I would assume they will
override the entries just like sdm850 boards (where I override it to set
these).
Alternatively I can keep it in DTSI, but it is not really property of
the SoC.
>
>
>> };
>>
>> - rx-pins {
>> + qup_uart6_4pin_rx: rx-pins {
>> pins = "gpio48";
>> function = "qup6";
>> - bias-pull-up;
>
> After your patch, where is the above bias set?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-02 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 16:42 [RFT PATCH v2 1/2] arm64: dts: qcom: sdm845-db845c: drop unneeded qup_spi0_default Krzysztof Kozlowski
2022-11-18 16:42 ` [RFT PATCH v2 2/2] arm64: dts: qcom: sdm845: align TLMM pin configuration with DT schema Krzysztof Kozlowski
2022-12-02 0:50 ` Doug Anderson
2022-12-02 8:15 ` Krzysztof Kozlowski [this message]
2022-12-02 14:36 ` Doug Anderson
2022-12-02 15:32 ` Krzysztof Kozlowski
2022-11-18 16:51 ` [RFT PATCH v2 1/2] arm64: dts: qcom: sdm845-db845c: drop unneeded qup_spi0_default Konrad Dybcio
2022-12-02 0:49 ` Doug Anderson
2022-12-02 8:17 ` Krzysztof Kozlowski
2022-12-02 14:38 ` Doug Anderson
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=68bcdf25-e8e3-f817-f213-efb0bce3f43a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=frkoenig@google.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.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;
as well as URLs for NNTP newsgroup(s).