All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/3] arm64: dts: qcom: Add Eliza-specific PM7550BA dtsi
Date: Thu, 14 May 2026 19:58:39 +0000	[thread overview]
Message-ID: <20260514195840.88D65C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260514-eliza-adsp-usb-v5-2-a21056ffd892@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Duplication of the entire PM7550BA PMIC Device Tree Include file to change the parent bus.
--

commit 5c503019cfe9b06711f49ae8a17f64175ea5c01d
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>

arm64: dts: qcom: Add Eliza-specific PM7550BA dtsi

This commit introduces a new Eliza-specific dtsi file for the PM7550BA PMIC.
It addresses hardware differences in the SPMI bus layout on the Eliza platform
by duplicating the PMIC definitions and placing them under spmi_bus0.

> The existing PM7550BA dtsi does not provide a way to describe this,
> so introduce an Eliza-specific variant with the appropriate bus
> configuration.
> 
> This duplication is required due to hardware differences in how the
> SPMI bus is exposed on this platform.

Is this duplication strictly required? While this isn't a bug, it seems
possible to avoid duplicating the file just to change the parent bus.

> diff --git a/arch/arm64/boot/dts/qcom/pm7550ba-eliza.dtsi b/arch/arm64/boot/dts/qcom/pm7550ba-eliza.dtsi
> new file mode 100644
> index 0000000000000..18692893ca418
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/pm7550ba-eliza.dtsi
> @@ -0,0 +1,70 @@
[ ... ]
> +&spmi_bus0 {
> +	pm7550ba: pmic@7 {
> +		compatible = "qcom,pm7550ba", "qcom,spmi-pmic";
> +		reg = <7 SPMI_USID>;
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		pm7550ba_temp_alarm: temp-alarm@a00 {

Could the common PMIC properties and sub-nodes be extracted into a shared
dtsi file using node appending?

If the shared file appended these thermal and GPIO definitions to an existing
pm7550ba label, the individual board files could define the empty base node
under their respective bus (such as spmi_bus0) and then include the shared
file.

Would this help prevent future maintenance issues when thermal trips or GPIO
definitions need to be synchronized across platforms?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260514-eliza-adsp-usb-v5-0-a21056ffd892@oss.qualcomm.com?part=2

  reply	other threads:[~2026-05-14 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 13:54 [PATCH v5 0/3] arm64: dts: qcom: eliza: Add ADSP and USB support Abel Vesa
2026-05-14 13:54 ` [PATCH v5 1/3] arm64: dts: qcom: eliza: Describe the ADSP and USB related nodes Abel Vesa
2026-05-14 13:54 ` [PATCH v5 2/3] arm64: dts: qcom: Add Eliza-specific PM7550BA dtsi Abel Vesa
2026-05-14 19:58   ` sashiko-bot [this message]
2026-05-14 13:54 ` [PATCH v5 3/3] arm64: dts: qcom: eliza-mtp: Enable USB and ADSP support Abel Vesa
2026-05-14 20:18   ` sashiko-bot

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=20260514195840.88D65C2BCB3@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.