From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
andersson@kernel.org, linus.walleij@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
rajendra.nayak@oss.qualcomm.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 v5 0/2] pinctrl: qcom: Introduce Pinctrl for Glymur
Date: Wed, 13 Aug 2025 09:31:30 +0200 [thread overview]
Message-ID: <17b90fbc-ccce-4eb1-b334-5fdef82c094c@kernel.org> (raw)
In-Reply-To: <20250813065533.3959018-1-pankaj.patil@oss.qualcomm.com>
On 13/08/2025 08:55, Pankaj Patil wrote:
> Introduce Top Level Mode Multiplexer dt-binding and driver for
> Qualcomm's next gen compute SoC - Glymur.
> Device tree changes aren't part of this series and will be posted separately after the official announcement of the Glymur SoC
>
> Changes in v5:
> Rebased on top of v6.17-rc1
> RESOUT_GPIO_N changed to lowercase in bindings and driver
>
> Changes in v4:
> Updated bindings to column length of 80 char
>
> Changes in v3:
> Fixed indentation for example tlmm node in bindings file
> Fixed s-o-b and review comments in the driver
>
> Changes in v2:
> Fixed dt-bindings error from example node's reg propery
> Fixed gpio-line-name maxItems
> Driver UFS_RESET macro updated
> Removed obsolete comment for pingroups
> Updated ngpio to include ufs_reset pin
Where are lore links? Why aren't you using b4?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-13 7:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 6:55 Pankaj Patil
2025-08-13 6:55 ` [PATCH v5 1/2] dt-bindings: pinctrl: qcom: Add Glymur pinctrl bindings Pankaj Patil
2025-09-03 10:08 ` Krzysztof Kozlowski
2025-09-03 11:01 ` Dmitry Baryshkov
2025-09-03 11:28 ` Krzysztof Kozlowski
2025-09-03 12:22 ` Dmitry Baryshkov
2025-09-04 12:59 ` Pankaj Patil
2025-08-13 6:55 ` [PATCH v5 2/2] pinctrl: qcom: Add glymur pinctrl driver Pankaj Patil
2025-08-13 10:14 ` Konrad Dybcio
2025-08-13 14:34 ` Bjorn Andersson
2025-09-03 9:53 ` Pankaj Patil
2025-09-03 10:09 ` Krzysztof Kozlowski
2025-09-04 19:34 ` Linus Walleij
2025-08-13 7:31 ` Krzysztof Kozlowski [this message]
2025-08-13 9:48 ` [PATCH v5 0/2] pinctrl: qcom: Introduce Pinctrl for Glymur Pankaj Patil
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=17b90fbc-ccce-4eb1-b334-5fdef82c094c@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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=pankaj.patil@oss.qualcomm.com \
--cc=rajendra.nayak@oss.qualcomm.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®