From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Richard Acayan <mailingradian@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/5] pinctrl: qcom: add sdm670 lpi tlmm
Date: Tue, 10 Mar 2026 12:30:32 +0100 [thread overview]
Message-ID: <3ecea1c4-cc2c-4a58-b62d-fbba2927fa54@oss.qualcomm.com> (raw)
In-Reply-To: <20260310012446.32226-4-mailingradian@gmail.com>
On 3/10/26 2:24 AM, Richard Acayan wrote:
> The Snapdragon 670 has an Low-Power Island (LPI) TLMM for configuring
> pins related to audio. Add the driver for this.
>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-03-10 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 1:24 [PATCH v2 0/5] SDM670 LPASS LPI pin controller support Richard Acayan
2026-03-10 1:24 ` [PATCH v2 1/5] dt-bindings: qcom: lpass-lpi-common: add reserved GPIOs property Richard Acayan
2026-03-10 9:00 ` Krzysztof Kozlowski
2026-03-10 1:24 ` [PATCH v2 2/5] dt-bindings: pinctrl: qcom: Add SDM670 LPASS LPI pinctrl Richard Acayan
2026-03-10 9:01 ` Krzysztof Kozlowski
2026-03-10 1:24 ` [PATCH v2 3/5] pinctrl: qcom: add sdm670 lpi tlmm Richard Acayan
2026-03-10 11:30 ` Konrad Dybcio [this message]
2026-03-10 1:24 ` [PATCH v2 4/5] arm64: dts: qcom: sdm670: add lpi pinctrl Richard Acayan
2026-03-10 3:46 ` Dmitry Baryshkov
2026-03-10 1:24 ` [PATCH v2 5/5] arm64: dts: qcom: sdm670-google: add reserved lpi gpios Richard Acayan
2026-03-10 11:26 ` Konrad Dybcio
2026-03-10 1:29 ` [PATCH v2 0/5] SDM670 LPASS LPI pin controller support Richard Acayan
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=3ecea1c4-cc2c-4a58-b62d-fbba2927fa54@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=robh@kernel.org \
--cc=srini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.