mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viken Dadhaniya <quic_vdadhani@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: <andersson@kernel.org>, <konradybcio@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <quic_msavaliy@quicinc.com>,
	<quic_anupkulk@quicinc.com>
Subject: Re: [PATCH v3] arm64: dts: qcom: sa8775p: Add default pin configurations for QUP SEs
Date: Fri, 9 May 2025 14:35:10 +0530	[thread overview]
Message-ID: <73cc2db3-8692-4da7-8cfb-29c2450a706d@quicinc.com> (raw)
In-Reply-To: <xvmk4paonzafxm5aesu67ggkwpdak2ughhi35wap45rjtuplsk@xe52pvnudsbp>



On 5/3/2025 11:11 AM, Dmitry Baryshkov wrote:
> On Tue, Apr 29, 2025 at 11:03:34PM +0530, Viken Dadhaniya wrote:
>> Default pinctrl configurations for all QUP (Qualcomm Universal Peripheral)
>> Serial Engines (SEs) are missing in the SoC device tree. These
>> configurations are required by client teams when enabling any SEs as I2C,
>> SPI, or Serial protocols.
>>
>> Add default pin configurations for Serial Engines (SEs) for all supported
>> protocols, including I2C, SPI, and UART, to the sa8775p device tree.  This
>> change facilitates slave device driver clients to enable usecase with
>> minimal modifications.
>>
>> Remove duplicate pin configurations from target-specific file as same pin
>> configuration is included in the SoC device tree.
>>
>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
>> ---
>> v2 -> v3:
>>
>> - Remove duplicate pin configurations from target-specific file.
>>
>> v2 Link: https://lore.kernel.org/lkml/20250324151047.842648-1-quic_vdadhani@quicinc.com/
>>
>> v1 -> v2:
>>
>> - Drop drive-strength and bias property from soc dtsi.
>> - Update commit log.
>>
>> v1 Link: https://lore.kernel.org/lkml/20250225154136.3052757-1-quic_vdadhani@quicinc.com/
>> ---
>> ---
>> ---
>>   arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi |  35 -
>>   arch/arm64/boot/dts/qcom/sa8775p.dtsi      | 750 +++++++++++++++++++++
>>   2 files changed, 750 insertions(+), 35 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>> index 967913169539..3b4243ef37e7 100644
>> --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>> @@ -508,15 +508,11 @@ queue3 {
>>   
>>   &i2c11 {
>>   	clock-frequency = <400000>;
>> -	pinctrl-0 = <&qup_i2c11_default>;
>> -	pinctrl-names = "default";
>>   	status = "okay";
>>   };
>>   
>>   &i2c18 {
>>   	clock-frequency = <400000>;
>> -	pinctrl-0 = <&qup_i2c18_default>;
>> -	pinctrl-names = "default";
>>   	status = "okay";
>>   };
>>   
>> @@ -678,8 +674,6 @@ &sleep_clk {
>>   };
>>   
>>   &spi16 {
>> -	pinctrl-0 = <&qup_spi16_default>;
>> -	pinctrl-names = "default";
>>   	status = "okay";
>>   };
>>   
>> @@ -712,80 +706,53 @@ ethernet0_mdio: ethernet0-mdio-pins {
>>   		};
>>   	};
>>   
>> -	qup_uart10_default: qup-uart10-state {
>> -		pins = "gpio46", "gpio47";
>> -		function = "qup1_se3";
>> -	};
>> -
>>   	qup_spi16_default: qup-spi16-state {
>> -		pins = "gpio86", "gpio87", "gpio88", "gpio89";
>> -		function = "qup2_se2";
>>   		drive-strength = <6>;
>>   		bias-disable;
>>   	};
> 
> If you are movign parts of these pinstates to the sa8775p.dtsi, then you
> should also turn these declarations into label-based updates:
> 
> &qup_spi16_default {
> 	drive-strength = <6>;
> 	bias-disable;
> };
> 
> Otherwise the configuration is fragile: if the name gets changed, then
> two parts will not match.
> 

Sure, Updated in v4.

>>   
>>   	qup_i2c11_default: qup-i2c11-state {
>> -		pins = "gpio48", "gpio49";
>> -		function = "qup1_se4";
>>   		drive-strength = <2>;
>>   		bias-pull-up;
>>   	};
>>   
>>
> 

      reply	other threads:[~2025-05-09  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 17:33 Viken Dadhaniya
2025-04-30 11:22 ` Mukesh Kumar Savaliya
2025-05-03  5:41 ` Dmitry Baryshkov
2025-05-09  9:05   ` Viken Dadhaniya [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=73cc2db3-8692-4da7-8cfb-29c2450a706d@quicinc.com \
    --to=quic_vdadhani@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_anupkulk@quicinc.com \
    --cc=quic_msavaliy@quicinc.com \
    --cc=robh@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

all inboxes | Powered by JetHome®