Re: [PATCH v5 11/11] arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm
From: Komal Bajaj
Date: Fri Jul 17 2026 - 05:24:39 EST
On 7/17/2026 12:03 AM, Konrad Dybcio wrote:
On 7/15/26 3:41 PM, Komal Bajaj wrote:Development initially started with firmware builds that did not have Access Policy enabled.
Well then, I'm no less than surprised since we have DTs for 3 boards
On 7/15/2026 3:57 PM, Konrad Dybcio wrote:
On 7/7/26 6:36 PM, Komal Bajaj wrote:Yes, with Access Policy enabled, it becomes boot-critical.
On 7/2/2026 4:25 PM, Konrad Dybcio wrote:I'm not sure how to read your response. In other words - is this
On 7/2/26 11:50 AM, Komal Bajaj wrote:Yes, some GPIOs are reserved for secure-world use and are therefore not accessible from the non-secure world.
Add gpio-reserved-ranges property to the tlmm node for all threeThese are generally added to prevent non-secure access upon TLMM
Shikra EVK variants (CQM, CQS, IQS) to mark GPIOs used by the
SoC internally and not available for general use.
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.
I will update the commit message accordingly.
patch boot-critical?
in -next right now that I'm learning can't possibly boot..
I understand you might have disabled that at some point during the
development, but it's clearly not the configuration that's supported
by any means. Please make sure to take that into account next time.
Recently, firmware has since been updated to enable Access Policy, which makes these GPIOs boot-critical and requires this change.
If its needed, I can add Fixes tag.
For this issue, since the pins seem common, perhaps moving them to
the SoM DTSI makes more sense. And this most definitely needs 'fixes'
tags.
Makes sense. I'll move it to the SoM DTSI in the next revision.
Thanks
Komal
Konrad