From: Krzysztof Kozlowski <krzk@kernel.org>
To: Richard Acayan <mailingradian@gmail.com>
Cc: 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 1/5] dt-bindings: qcom: lpass-lpi-common: add reserved GPIOs property
Date: Tue, 10 Mar 2026 10:00:24 +0100 [thread overview]
Message-ID: <20260310-rigorous-whimsical-pudu-5f4df6@quoll> (raw)
In-Reply-To: <20260310012446.32226-2-mailingradian@gmail.com>
On Mon, Mar 09, 2026 at 09:24:42PM -0400, Richard Acayan wrote:
> There can be reserved GPIOs on the LPASS LPI pin controller to possibly
> control sensors. Add the property for reserved GPIOs so they can be
> avoided appropriately.
>
> Adapted from the same entry in qcom,tlmm-common.yaml.
>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> ---
> .../devicetree/bindings/pinctrl/qcom,lpass-lpi-common.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,lpass-lpi-common.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,lpass-lpi-common.yaml
> index 619341dd637c..0c3fa5d597e0 100644
> --- a/Documentation/devicetree/bindings/pinctrl/qcom,lpass-lpi-common.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/qcom,lpass-lpi-common.yaml
> @@ -27,6 +27,12 @@ properties:
> gpio-ranges:
> maxItems: 1
>
> + gpio-reserved-ranges:
> + description:
> + Pins can be reserved for trusted applications or for LPASS, thereby
> + inaccessible from the OS. This property can be used to mark the pins
> + which resources should not be accessed by the OS.
minItems: 1
maxItems: 30
I guess to have somoe sort reasonable limit.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-10 9:00 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 [this message]
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
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=20260310-rigorous-whimsical-pudu-5f4df6@quoll \
--to=krzk@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox