From: Viken Dadhaniya <quic_vdadhani@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: <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 v1] arm64: dts: qcom: sa8775p: Add default pin configurations for QUP SEs
Date: Mon, 24 Mar 2025 22:14:03 +0530 [thread overview]
Message-ID: <f565fee7-b222-4e6b-b022-68aed9a7d9ea@quicinc.com> (raw)
In-Reply-To: <keszvik5mrobfkdpgdz5rnl5l7tihgbpyd4en3dflmaflyl7io@d4my7wdrtkyg>
On 3/4/2025 10:05 AM, Bjorn Andersson wrote:
> On Tue, Feb 25, 2025 at 09:11:36PM +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.
>>
>> Additionally, move default pin configurations from target-specific files to
>> the SoC device tree file, as all possible pin configurations are now
>> comprehensively included in the SoC device tree, similar to other SoCs.
>>
>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 88 --
>> arch/arm64/boot/dts/qcom/sa8775p.dtsi | 908 +++++++++++++++++++++
>> 2 files changed, 908 insertions(+), 88 deletions(-)
>>
> [..]
>> diff --git a/arch/arm64/boot/dts/qcom/sa8775p.dtsi b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> [..]
>> + qup_i2c0_default: qup-i2c0-state {
>> + pins = "gpio20", "gpio21";
>> + function = "qup0_se0";
>> + drive-strength = <2>;
>> + bias-pull-up;
>
> Look at other examples, such as sc7280.dtsi, and you will see that
> drive-strength and bias are considered board-specific properties and
> should thereby not go in the soc.dtsi file.
>
Removed drive-strength and bias in v2.
> Thanks,
> Bjorn
prev parent reply other threads:[~2025-03-24 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 15:41 [PATCH v1] arm64: dts: qcom: sa8775p: Add default pin configurations for QUP SEs Viken Dadhaniya
2025-03-04 4:35 ` Bjorn Andersson
2025-03-24 16:44 ` 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=f565fee7-b222-4e6b-b022-68aed9a7d9ea@quicinc.com \
--to=quic_vdadhani@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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