From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Viken Dadhaniya <quic_vdadhani@quicinc.com>,
<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>
Cc: <quic_anupkulk@quicinc.com>
Subject: Re: [PATCH v3] arm64: dts: qcom: sa8775p: Add default pin configurations for QUP SEs
Date: Wed, 30 Apr 2025 16:52:03 +0530 [thread overview]
Message-ID: <c94c659a-ca16-4f79-8522-62b985b7db9b@quicinc.com> (raw)
In-Reply-To: <20250429173334.303003-1-quic_vdadhani@quicinc.com>
Change looks good to me.
On 4/29/2025 11:03 PM, 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>
Acked-by: Mukesh Kumar Savaliya <quic_msavaliy@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/
> ---
next prev parent reply other threads:[~2025-04-30 11:22 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 [this message]
2025-05-03 5:41 ` Dmitry Baryshkov
2025-05-09 9:05 ` Viken Dadhaniya
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=c94c659a-ca16-4f79-8522-62b985b7db9b@quicinc.com \
--to=quic_msavaliy@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_vdadhani@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®