[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c6bebd3-6799-5df5-fa46-25e1b7cfd60a@linaro.org>
Date: Tue, 4 Jul 2023 13:08:01 +0200
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Komal Bajaj <quic_kbajaj@...cinc.com>, agross@...nel.org,
andersson@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qdu1000: Add reserved gpio list
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 <quic_kbajaj@...cinc.com>
> ---
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";
> };
Powered by blists - more mailing lists