Add reserved gpio list for QDU1000 and QRU1000 SoCs
which will not be used by HLOS.
Signed-off-by: Komal Bajaj <[email protected]>
---
arch/arm64/boot/dts/qcom/qdu1000-idp.dts | 4 ++++
arch/arm64/boot/dts/qcom/qru1000-idp.dts | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
index 1d22f87fd238..0496e87ddfd5 100644
--- a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
+++ b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
@@ -471,6 +471,10 @@ &sdhc {
status = "okay";
};
+&tlmm {
+ gpio-reserved-ranges = <28 2>;
+};
+
&uart7 {
status = "okay";
};
diff --git a/arch/arm64/boot/dts/qcom/qru1000-idp.dts b/arch/arm64/boot/dts/qcom/qru1000-idp.dts
index 2cc893ae4d10..80dadd2f30a3 100644
--- a/arch/arm64/boot/dts/qcom/qru1000-idp.dts
+++ b/arch/arm64/boot/dts/qcom/qru1000-idp.dts
@@ -448,6 +448,10 @@ &qupv3_id_0 {
status = "okay";
};
+&tlmm {
+ gpio-reserved-ranges = <28 2>;
+};
+
&uart7 {
status = "okay";
};
--
2.40.1
On 4.07.2023 12:22, Komal Bajaj wrote:
> Add reserved gpio list for QDU1000 and QRU1000 SoCs
> which will not be used by HLOS.
>
> Signed-off-by: Komal Bajaj <[email protected]>
> ---
Generally such changes to board files are split into per-board
commits.
Can you explain why these GPIOs will be inaccessible? Some secure
I2C peripheral, I'd guess?
Konrad
> arch/arm64/boot/dts/qcom/qdu1000-idp.dts | 4 ++++
> arch/arm64/boot/dts/qcom/qru1000-idp.dts | 4 ++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
> index 1d22f87fd238..0496e87ddfd5 100644
> --- a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
> +++ b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
> @@ -471,6 +471,10 @@ &sdhc {
> status = "okay";
> };
>
> +&tlmm {
> + gpio-reserved-ranges = <28 2>;
> +};
> +
> &uart7 {
> status = "okay";
> };
> diff --git a/arch/arm64/boot/dts/qcom/qru1000-idp.dts b/arch/arm64/boot/dts/qcom/qru1000-idp.dts
> index 2cc893ae4d10..80dadd2f30a3 100644
> --- a/arch/arm64/boot/dts/qcom/qru1000-idp.dts
> +++ b/arch/arm64/boot/dts/qcom/qru1000-idp.dts
> @@ -448,6 +448,10 @@ &qupv3_id_0 {
> status = "okay";
> };
>
> +&tlmm {
> + gpio-reserved-ranges = <28 2>;
> +};
> +
> &uart7 {
> status = "okay";
> };
On 7/4/2023 4:38 PM, Konrad Dybcio wrote:
> On 4.07.2023 12:22, Komal Bajaj wrote:
>> Add reserved gpio list for QDU1000 and QRU1000 SoCs
>> which will not be used by HLOS.
>>
>> Signed-off-by: Komal Bajaj <[email protected]>
>> ---
> Generally such changes to board files are split into per-board
> commits.
Sure, will split into per-board commits.
>
> Can you explain why these GPIOs will be inaccessible? Some secure
> I2C peripheral, I'd guess?
These GPIOs are needed by Modem subsystem.
Thanks
Komal
>
> Konrad
>> arch/arm64/boot/dts/qcom/qdu1000-idp.dts | 4 ++++
>> arch/arm64/boot/dts/qcom/qru1000-idp.dts | 4 ++++
>> 2 files changed, 8 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> index 1d22f87fd238..0496e87ddfd5 100644
>> --- a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> +++ b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> @@ -471,6 +471,10 @@ &sdhc {
>> status = "okay";
>> };
>>
>> +&tlmm {
>> + gpio-reserved-ranges = <28 2>;
>> +};
>> +
>> &uart7 {
>> status = "okay";
>> };
>> diff --git a/arch/arm64/boot/dts/qcom/qru1000-idp.dts b/arch/arm64/boot/dts/qcom/qru1000-idp.dts
>> index 2cc893ae4d10..80dadd2f30a3 100644
>> --- a/arch/arm64/boot/dts/qcom/qru1000-idp.dts
>> +++ b/arch/arm64/boot/dts/qcom/qru1000-idp.dts
>> @@ -448,6 +448,10 @@ &qupv3_id_0 {
>> status = "okay";
>> };
>>
>> +&tlmm {
>> + gpio-reserved-ranges = <28 2>;
>> +};
>> +
>> &uart7 {
>> status = "okay";
>> };