From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Anurag Pateriya <apateriy@qti.qualcomm.com>
Subject: Re: [PATCH v5 11/11] arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
Date: Tue, 7 Jul 2026 22:06:05 +0530 [thread overview]
Message-ID: <97b205e8-5ab7-4205-b1dc-cbcb0497987d@oss.qualcomm.com> (raw)
In-Reply-To: <9c1aab59-14b2-4811-b778-8e96645bd65b@oss.qualcomm.com>
On 7/2/2026 4:25 PM, Konrad Dybcio wrote:
> On 7/2/26 11:50 AM, Komal Bajaj wrote:
>> Add gpio-reserved-ranges property to the tlmm node for all three
>> Shikra EVK variants (CQM, CQS, IQS) to mark GPIOs used by the
>> SoC internally and not available for general use.
> These are generally added to prevent non-secure access upon TLMM
> probe, i.e. the board won't boot if some of them are not protected.
>
> I assume the proposed set contains both ones that are _absolutely
> forbidden_ for Linux to touch, but also ones that are dedicated to
> some specific purpose that Linux _shouldn't_ touch.
Yes, some GPIOs are reserved for secure-world use and are therefore not
accessible from the non-secure world.
I will update the commit message accordingly.
>
> Please add comments, like in glymur-crd.dtsi:
>
> gpio-reserved-ranges = <4 4>, /* EC TZ Secure I3C */
> <10 2>, /* OOB UART */
> <44 4>; /* Security SPI (TPM) */
>
> explaining what these pins are.
Sure, will add this info.
Thanks
Komal
>
> If any of them are boot-critical, squash this into the introductory
> change
>
> Konrad
prev parent reply other threads:[~2026-07-07 16:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:50 [PATCH v5 00/11] arm64: dts: qcom: Extend Shikra device tree with peripheral and subsystem support Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 01/11] dt-bindings: interconnect: qcom-bwmon: Add Shikra cpu-bwmon compatible Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 02/11] arm64: dts: qcom: Add QUPv3 configuration for Shikra Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 03/11] arm64: dts: qcom: shikra: Add DDR BWMON support Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 04/11] arm64: dts: qcom: shikra: Add cpufreq-hw, EPSS L3 interconnect and OPP tables Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 05/11] arm64: dts: qcom: shikra: Add SMP2P nodes Komal Bajaj
2026-07-02 10:56 ` Konrad Dybcio
2026-07-02 9:50 ` [PATCH v5 06/11] arm64: dts: qcom: shikra: Add CDSP, LPAICP, MPSS remoteproc PAS nodes Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 07/11] arm64: dts: qcom: shikra: Enable CDSP, LPAICP and MPSS on EVK boards Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 08/11] arm64: dts: qcom: shikra: Enable TSENS and thermal zones Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 09/11] arm64: dts: qcom: shikra: add WiFi node support Komal Bajaj
2026-07-02 10:57 ` Konrad Dybcio
2026-07-02 9:50 ` [PATCH v5 10/11] arm64: dts: qcom: shikra: Enable Bluetooth and WiFi on EVK boards Komal Bajaj
2026-07-02 10:59 ` Konrad Dybcio
2026-07-07 13:43 ` Komal Bajaj
2026-07-02 11:56 ` Dmitry Baryshkov
2026-07-07 13:43 ` Komal Bajaj
2026-07-02 9:50 ` [PATCH v5 11/11] arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm Komal Bajaj
2026-07-02 10:55 ` Konrad Dybcio
2026-07-07 16:36 ` Komal Bajaj [this message]
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=97b205e8-5ab7-4205-b1dc-cbcb0497987d@oss.qualcomm.com \
--to=komal.bajaj@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=andersson@kernel.org \
--cc=apateriy@qti.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vkoul@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