From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: document the Eliza Top Level Mode Multiplexer
Date: Sun, 8 Feb 2026 11:04:06 +0100 [thread overview]
Message-ID: <d15efd8e-079d-44e7-bc2e-63d21f219ade@kernel.org> (raw)
In-Reply-To: <yhnnlbvcqgtaseoiarii4rfsmiem56hxsiuibf3kyux5ftebgy@dhkhij3qq7sk>
On 29/01/2026 11:59, Abel Vesa wrote:
>>>
>>>> +
>>>> + gpio-line-names:
>>>> + maxItems: 185
>>>
>>> 186, your first GPIO is 0 and last is 185.
>>
>> Wait, are all of these wrong then?
>>
>> $ grep -r "gpio-line-names" Documentation/devicetree/bindings/pinctrl/qcom,sm8[3-7]50* -A 3 |grep maxItems:
>> Documentation/devicetree/bindings/pinctrl/qcom,sm8350-tlmm.yaml- maxItems: 203
>> Documentation/devicetree/bindings/pinctrl/qcom,sm8450-tlmm.yaml- maxItems: 210
>> Documentation/devicetree/bindings/pinctrl/qcom,sm8550-tlmm.yaml- maxItems: 210
>> Documentation/devicetree/bindings/pinctrl/qcom,sm8650-tlmm.yaml- maxItems: 210
>> Documentation/devicetree/bindings/pinctrl/qcom,sm8750-tlmm.yaml- maxItems: 215
>> $ grep -r "UFS_RESET\"" drivers/pinctrl/qcom/pinctrl-sm8[3-7]50.c
>> drivers/pinctrl/qcom/pinctrl-sm8350.c: PINCTRL_PIN(203, "UFS_RESET"),
>> drivers/pinctrl/qcom/pinctrl-sm8450.c: PINCTRL_PIN(210, "UFS_RESET"),
>> drivers/pinctrl/qcom/pinctrl-sm8550.c: PINCTRL_PIN(210, "UFS_RESET"),
>> drivers/pinctrl/qcom/pinctrl-sm8650.c: PINCTRL_PIN(210, "UFS_RESET"),
>> drivers/pinctrl/qcom/pinctrl-sm8750.c: PINCTRL_PIN(215, "UFS_RESET"),
>
> 185 is actually correct, because ufs_reset doesn't count.
But you wrote in other part you have 186 GPIOs. I don't mention here
UFSRESET. If above is correct, then rest of your patch has some issue.
Anyway, something needs fixing.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-08 10:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 15:47 [PATCH v2 0/2] pinctrl: qcom: Add support for Qualcomm Eliza SoC Abel Vesa
2026-01-27 15:47 ` [PATCH v2 1/2] dt-bindings: pinctrl: document the Eliza Top Level Mode Multiplexer Abel Vesa
2026-01-28 11:38 ` Krzysztof Kozlowski
2026-01-28 17:22 ` Abel Vesa
2026-01-28 19:58 ` Krzysztof Kozlowski
2026-01-29 8:44 ` Abel Vesa
2026-01-29 10:34 ` Konrad Dybcio
2026-01-29 10:41 ` Abel Vesa
2026-01-29 10:45 ` Konrad Dybcio
2026-01-29 10:57 ` Abel Vesa
2026-01-29 11:12 ` Abel Vesa
2026-01-29 12:04 ` Konrad Dybcio
2026-01-29 12:42 ` Abel Vesa
2026-01-29 14:11 ` Konrad Dybcio
2026-01-30 8:18 ` Abel Vesa
2026-01-29 10:54 ` Abel Vesa
2026-01-29 10:59 ` Abel Vesa
2026-02-08 10:04 ` Krzysztof Kozlowski [this message]
2026-02-16 12:57 ` Abel Vesa
2026-01-27 15:47 ` [PATCH v2 2/2] pinctrl: qcom: Add Eliza pinctrl driver Abel Vesa
2026-01-27 19:13 ` [PATCH v2 0/2] pinctrl: qcom: Add support for Qualcomm Eliza SoC Bjorn Andersson
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=d15efd8e-079d-44e7-bc2e-63d21f219ade@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@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