From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Mayank Grover" <groverm@codeaurora.org>
Subject: [PATCH v2 0/2] pinctrl: qcom: add support for TLMM on SAR2130P
Date: Fri, 18 Oct 2024 11:42:38 +0300 [thread overview]
Message-ID: <20241018-sar2130p-tlmm-v2-0-11a1d09a6e5f@linaro.org> (raw)
Add driver for the pin controlling device as present on the Qualcomm
SAR2130P platform.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
Changes in v2:
- Fixed gpio-reserved-ranges and the patttern for the pins to match the
number of GPIOs (Krzysztof)
- Switched from .remove_new to .remove (Uwe)
- Link to v1: https://lore.kernel.org/r/20241017-sar2130p-tlmm-v1-0-8d8f0bd6f19a@linaro.org
---
Dmitry Baryshkov (2):
dt-bindings: pinctrl : qcom: document SAR2130P TLMM
pinctrl: qcom: add support for TLMM on SAR2130P
.../bindings/pinctrl/qcom,sar2130p-tlmm.yaml | 138 ++
drivers/pinctrl/qcom/Kconfig.msm | 8 +
drivers/pinctrl/qcom/Makefile | 1 +
drivers/pinctrl/qcom/pinctrl-sar2130p.c | 1505 ++++++++++++++++++++
4 files changed, 1652 insertions(+)
---
base-commit: 7df1e7189cecb6965ce672e820a5ec6cf499b65b
change-id: 20241017-sar2130p-tlmm-65836c137fa3
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
next reply other threads:[~2024-10-18 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 8:42 Dmitry Baryshkov [this message]
2024-10-18 8:42 ` [PATCH v2 1/2] dt-bindings: pinctrl : qcom: document SAR2130P TLMM Dmitry Baryshkov
2024-10-18 8:44 ` Krzysztof Kozlowski
2024-10-18 8:42 ` [PATCH v2 2/2] pinctrl: qcom: add support for TLMM on SAR2130P Dmitry Baryshkov
2024-10-22 12:45 ` [PATCH v2 0/2] " Linus Walleij
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=20241018-sar2130p-tlmm-v2-0-11a1d09a6e5f@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=groverm@codeaurora.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=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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).