From: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
andersson@kernel.org, linus.walleij@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
quic_rjendra@quicinc.com
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: qcom: Add glymur pinctrl driver
Date: Fri, 18 Jul 2025 19:32:36 +0530 [thread overview]
Message-ID: <a2be3ff9-d364-4a6e-a8e2-e0391e979b11@oss.qualcomm.com> (raw)
In-Reply-To: <19b62fb0-fb49-4a90-bff4-f5634547f2fe@kernel.org>
On 7/17/2025 8:09 PM, Krzysztof Kozlowski wrote:
> On 17/07/2025 13:52, Konrad Dybcio wrote:
>>> +static const struct msm_pinctrl_soc_data glymur_tlmm = {
>>> + .pins = glymur_pins,
>>> + .npins = ARRAY_SIZE(glymur_pins),
>>> + .functions = glymur_functions,
>>> + .nfunctions = ARRAY_SIZE(glymur_functions),
>>> + .groups = glymur_groups,
>>> + .ngroups = ARRAY_SIZE(glymur_groups),
>>> + .ngpios = 250,
>> 251 (0..=250, incl. ufs reset)
>
> The binding said 238 GPIOs...
>
>> Konrad
>
> Best regards,
> Krzysztof
Will correct the bindings along with the driver fixes in v2.
next prev parent reply other threads:[~2025-07-18 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 15:08 [PATCH 0/2] pinctrl: qcom: Introduce Pinctrl for Glymur Pankaj Patil
2025-07-16 15:08 ` [PATCH 1/2] dt-bindings: pinctrl: qcom: Add Glymur pinctrl bindings Pankaj Patil
2025-07-16 16:33 ` Rob Herring (Arm)
2025-07-16 15:08 ` [PATCH 2/2] pinctrl: qcom: Add glymur pinctrl driver Pankaj Patil
2025-07-17 11:13 ` Abel Vesa
2025-07-17 11:52 ` Konrad Dybcio
2025-07-17 14:39 ` Krzysztof Kozlowski
2025-07-18 14:02 ` Pankaj Patil [this message]
2025-07-20 4:09 ` 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=a2be3ff9-d364-4a6e-a8e2-e0391e979b11@oss.qualcomm.com \
--to=pankaj.patil@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--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
all inboxes | Powered by JetHome®