Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Komal Bajaj <quic_kbajaj@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <agross@kernel.org>,
	<andersson@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: qdu1000: Add reserved gpio list
Date: Tue, 4 Jul 2023 17:26:18 +0530	[thread overview]
Message-ID: <422ffe93-e390-7379-70ad-e56f73e1da44@quicinc.com> (raw)
In-Reply-To: <1c6bebd3-6799-5df5-fa46-25e1b7cfd60a@linaro.org>



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 <quic_kbajaj@quicinc.com>
>> ---
> 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";
>>   };


      reply	other threads:[~2023-07-04 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 10:22 [PATCH] arm64: dts: qcom: qdu1000: Add reserved gpio list Komal Bajaj
2023-07-04 11:08 ` Konrad Dybcio
2023-07-04 11:56   ` 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=422ffe93-e390-7379-70ad-e56f73e1da44@quicinc.com \
    --to=quic_kbajaj@quicinc.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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