All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yixun Lan" <dlan@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: spacemit: drop unnecessary power supply from PCIe
Date: Thu, 14 May 2026 00:54:34 +0000	[thread overview]
Message-ID: <20260514005435.484B5C2BCB8@smtp.kernel.org> (raw)
In-Reply-To: <20260513-k1-pcie-fix-supply-v1-1-4eecbdd44ebe@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing `vpcie3v3-supply` from the PCIe controller node breaks power sequencing because the `spacemit,k1-pcie` driver expects it on the controller node.
--

commit ab7558e23a3bb4900f7961804151870f4c1f99fe
Author: Yixun Lan <dlan@kernel.org>

riscv: dts: spacemit: drop unnecessary power supply from PCIe

This commit removes the vpcie3v3-supply property from the PCIe controller
nodes in the Banana Pi F3 and Milk-V Jupiter device trees. The commit message
states that the supply belongs to the child port node rather than the Root
Complex, aligning with the dt-binding documentation.

Link: https://lore.kernel.org/all/20251113214540.2623070-4-elder@riscstar.com/

> diff --git a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> index e20daa50a152f..c70081856606f 100644
> --- a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> +++ b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> @@ -316,7 +316,6 @@ &pcie1_port {
>  };
>  
>  &pcie1 {
> -	vpcie3v3-supply = <&pcie_vcc_3v3>;

Will removing the vpcie3v3-supply property from the controller node break
power sequencing?

Looking at drivers/pci/controller/dwc/pcie-spacemit-k1.c, the host driver
calls devm_regulator_get_enable(dev, "vpcie3v3") during k1_pcie_probe().

Without this property on the controller node, won't the driver fall back
to a dummy regulator?

Since the spacemit-k1-pcie driver does not currently integrate with the PCI
power control framework (by calling pci_pwrctrl_create_devices()), does any
driver in the kernel actually control the power supply for the child port node?

While this issue might be masked on the Banana Pi F3 and Milk-V Jupiter
boards because their vpcie3v3 regulators are defined as regulator-always-on,
does this change break dynamic power management for the PCIe slots?

Should the host driver be updated to adopt the pci_pwrctrl framework before
dropping this property from the device tree?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-k1-pcie-fix-supply-v1-1-4eecbdd44ebe@kernel.org?part=1

  parent reply	other threads:[~2026-05-14  0:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  2:14 [PATCH] riscv: dts: spacemit: drop unnecessary power supply from PCIe Yixun Lan
2026-05-13  2:14 ` Yixun Lan
2026-05-13  8:24 ` Anand Moon
2026-05-13  8:24   ` Anand Moon
2026-05-14  0:54 ` sashiko-bot [this message]
2026-05-15  7:47   ` Yixun Lan

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=20260514005435.484B5C2BCB8@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@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.