From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: agross@kernel.org, bjorn.andersson@linaro.org, linus.walleij@linaro.org
Cc: konrad.dybcio@somainline.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] pinctrl: add support for SM8450 LPASS LPI pinctrl
Date: Tue, 16 Aug 2022 19:01:55 +0100 [thread overview]
Message-ID: <20220816180157.6711-1-srinivas.kandagatla@linaro.org> (raw)
This patchset adds pinctrl driver to support pin configuration for LPASS
(Low Power Audio SubSystem) LPI (Low Power Island) pinctrl on SM8450.
This IP is an additional pin control block for Audio Pins on top the
existing SoC Top level pin-controller.
Tested this on SM8450 MTP
Thanks,
Srini
Changes since v1:
- no code changes only minor fixes to bindings as suggested by Rob
Srinivas Kandagatla (2):
dt-bindings: pinctrl: qcom: Add sm8450 lpass lpi pinctrl bindings
pinctrl: qcom: Add sm8450 lpass lpi pinctrl driver
.../qcom,sm8450-lpass-lpi-pinctrl.yaml | 136 ++++++++++
drivers/pinctrl/qcom/Kconfig | 9 +
drivers/pinctrl/qcom/Makefile | 1 +
.../pinctrl/qcom/pinctrl-sm8450-lpass-lpi.c | 240 ++++++++++++++++++
4 files changed, 386 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml
create mode 100644 drivers/pinctrl/qcom/pinctrl-sm8450-lpass-lpi.c
--
2.21.0
next reply other threads:[~2022-08-16 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 18:01 Srinivas Kandagatla [this message]
2022-08-16 18:01 ` [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add sm8450 lpass lpi pinctrl bindings Srinivas Kandagatla
2022-08-17 6:07 ` Krzysztof Kozlowski
2022-08-16 18:01 ` [PATCH v2 2/2] pinctrl: qcom: Add sm8450 lpass lpi pinctrl driver Srinivas Kandagatla
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=20220816180157.6711-1-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.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).