From: Linus Walleij <linusw@kernel.org>
To: Richard Acayan <mailingradian@gmail.com>
Cc: Bjorn Andersson <andersson@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 v5 4/4] arm64: dts: qcom: sdm670: add lpi pinctrl
Date: Tue, 7 Apr 2026 09:03:11 +0200 [thread overview]
Message-ID: <CAD++jLk5VzmH93KcfY_JQf7qidoroiuDyQyD4GT73uq7rAU4kQ@mail.gmail.com> (raw)
In-Reply-To: <20260331200658.1306-5-mailingradian@gmail.com>
On Tue, Mar 31, 2026 at 10:06 PM Richard Acayan <mailingradian@gmail.com> wrote:
> The Snapdragon 670 has a separate TLMM for audio pins. Add the device
> node for it.
>
> Also add reserved GPIOs for the Pixel 3a, which blocks access to the
> sensor GPIOs.
>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Acked-by: Linus Walleij <linusw@kernel.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2026-04-07 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 20:06 [PATCH v5 0/4] SDM670 LPASS LPI pin controller support Richard Acayan
2026-03-31 20:06 ` [PATCH v5 1/4] dt-bindings: qcom: lpass-lpi-common: add reserved GPIOs property Richard Acayan
2026-03-31 20:06 ` [PATCH v5 2/4] dt-bindings: pinctrl: qcom: Add SDM670 LPASS LPI pinctrl Richard Acayan
2026-03-31 20:06 ` [PATCH v5 3/4] pinctrl: qcom: add sdm670 lpi tlmm Richard Acayan
2026-03-31 20:06 ` [PATCH v5 4/4] arm64: dts: qcom: sdm670: add lpi pinctrl Richard Acayan
2026-04-07 7:03 ` Linus Walleij [this message]
2026-04-07 7:02 ` [PATCH v5 0/4] SDM670 LPASS LPI pin controller support Linus Walleij
2026-05-13 19:09 ` (subset) " Bjorn Andersson
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=CAD++jLk5VzmH93KcfY_JQf7qidoroiuDyQyD4GT73uq7rAU4kQ@mail.gmail.com \
--to=linusw@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).