From: Vinod Koul <vkoul@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>, Andy Gross <agross@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/2] pinctrl: qcom: Add SM8350 pinctrl support
Date: Fri, 5 Feb 2021 19:31:30 +0530 [thread overview]
Message-ID: <20210205140132.274242-1-vkoul@kernel.org> (raw)
This adds binding and driver for TLMM block found in SM8350 SoC
The binding is dependent on TLMM common binding from Bjorn:
https://lore.kernel.org/linux-arm-msm/20210126042650.1725176-1-bjorn.andersson@linaro.org
Changes in v6:
- Add rob and bjorn r-b
- removed quotes around 'defs' and drop the phandle for binding
Changes in v5:
- rebase and revise binding based on Bjorn's qcom common TLMM binding
Changes in v4:
- rename to qcom,sm8350-tlmm along with binding and driver structs
- fix some nits in binding pointer by Rob
Vinod Koul (2):
dt-bindings: pinctrl: qcom: Add SM8350 pinctrl bindings
pinctrl: qcom: Add SM8350 pinctrl driver
.../bindings/pinctrl/qcom,sm8350-pinctrl.yaml | 145 ++
drivers/pinctrl/qcom/Kconfig | 9 +
drivers/pinctrl/qcom/Makefile | 1 +
drivers/pinctrl/qcom/pinctrl-sm8350.c | 1649 +++++++++++++++++
4 files changed, 1804 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8350-pinctrl.yaml
create mode 100644 drivers/pinctrl/qcom/pinctrl-sm8350.c
--
2.26.2
next reply other threads:[~2021-02-05 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 14:01 Vinod Koul [this message]
2021-02-05 14:01 ` [PATCH v6 1/2] dt-bindings: pinctrl: qcom: Add SM8350 pinctrl bindings Vinod Koul
2021-02-05 14:01 ` [PATCH v6 2/2] pinctrl: qcom: Add SM8350 pinctrl driver Vinod Koul
2021-02-12 7:50 ` [PATCH v6 0/2] pinctrl: qcom: Add SM8350 pinctrl support 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=20210205140132.274242-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.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+dt@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;
as well as URLs for NNTP newsgroup(s).