From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xueyao An <xueyao.an@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: qcom: shikra: Unreserve GPIOs 14-17 blocking SPI5 access
Date: Thu, 20 Aug 2026 11:34:08 +0200 [thread overview]
Message-ID: <93e31d56-e9fc-4dba-8494-423df36c8ccb@kernel.org> (raw)
In-Reply-To: <20260820085347.822-1-xueyao.an@oss.qualcomm.com>
On 20/08/2026 10:53, Xueyao An wrote:
> GPIOs 14-17 were previously reserved in the tlmm gpio-reserved-ranges,
> preventing Linux from accessing SPI5. Since there is no TZ use case for
> these pins on Linux, they can be safely unreserved. Removing them from
> the reserved list across all three Shikra EVK variants (CQM, CQS, IQS)
> resolves the SPI5 access issue.
>
> Signed-off-by: Xueyao An <xueyao.an@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi | 1 -
> arch/arm64/boot/dts/qcom/shikra-iqs-som.dtsi | 1 -
> 2 files changed, 2 deletions(-)
Why would Linux need to access SPI5 if there is no user of it? Or is
there, but you skipped it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-20 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 8:53 [PATCH v1] arm64: dts: qcom: shikra: Unreserve GPIOs 14-17 blocking SPI5 access Xueyao An
2026-08-20 9:34 ` Krzysztof Kozlowski [this message]
2026-08-20 9:38 ` Abel Vesa
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=93e31d56-e9fc-4dba-8494-423df36c8ccb@kernel.org \
--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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xueyao.an@oss.qualcomm.com \
/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