From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
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: Thu, 29 Jan 2026 11:45:59 +0100 [thread overview]
Message-ID: <8360708d-5d82-4cbe-bf0c-31107ab07bac@oss.qualcomm.com> (raw)
In-Reply-To: <pdxrotmxjiebyj2gqx6buwupkydngxki6jgv4e6l6fmodzc5v2@yxky3civt3yz>
On 1/29/26 11:41 AM, Abel Vesa wrote:
> On 26-01-29 11:34:07, Konrad Dybcio wrote:
>> On 1/28/26 6:22 PM, Abel Vesa wrote:
>>> On 26-01-28 12:38:32, Krzysztof Kozlowski wrote:
>>>> On Tue, Jan 27, 2026 at 05:47:36PM +0200, Abel Vesa wrote:
>>>>> Document the Top Level Mode Multiplexer on the Eliza Platform.
>>>>>
>>>>> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>>>> ---
>>
>> [...]
>>
>>>>> +
>>>>> + gpio-line-names:
>>>>> + maxItems: 185
>>>>
>>>> 186, your first GPIO is 0 and last is 185.
>>>
>>> Actually it is 0 through 184. The 185 is ufs reset.
>>
>> The UFS reset also happens to be a GPIO..
>
> So the gpio-line-names should include the ufs reset,
> but the pattern not.
Why not?
Do you see a reference to ufs_reset anywhere in DT?
Konrad
next prev parent reply other threads:[~2026-01-29 10:46 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 [this message]
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
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=8360708d-5d82-4cbe-bf0c-31107ab07bac@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=krzk@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