All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] ARM: dts: aspeed: sanmiguel: Remove HSC nodes
@ 2026-07-30 13:11 Potin Lai
  2026-07-30 13:17 ` sashiko-bot
  0 siblings, 1 reply; 2+ messages in thread
From: Potin Lai @ 2026-07-30 13:11 UTC (permalink / raw)
  To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Joel Stanley,
	Andrew Jeffery, Patrick Williams
  Cc: devicetree, linux-arm-kernel, linux-aspeed, linux-kernel,
	Cosmo Chou, Mike Hsieh, Mik Lin, Potin Lai, Potin Lai

Remove Hot-Swap Controller (HSC) power monitor nodes from the DTS.

Due to design requirements, the HSC driver probing is moved to userspace.
Removing these nodes from the device tree prevents kernel-level automatic
driver probing and allows userspace to handle HSC device instantiation.

Signed-off-by: Potin Lai <potin.lai.pt@gmail.com>
---
 .../dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts   | 44 ----------------------
 1 file changed, 44 deletions(-)

diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts
index 3cc6e772cc8c..98f224d2c091 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts
@@ -442,50 +442,6 @@ &i2c8 {
 &i2c9 {
 	status = "okay";
 
-	pdb_mps_hsc1: power-monitor@10 {
-		compatible = "mps,mp5926";
-		reg = <0x10>;
-	};
-
-	pdb_ti_hsc1: power-monitor@11 {
-		compatible = "ti,lm5066i";
-		reg = <0x11>;
-		shunt-resistor-micro-ohms = <1000>;
-	};
-
-	pdb_mps_hsc2: power-monitor@12 {
-		compatible = "mps,mp5926";
-		reg = <0x12>;
-	};
-
-	pdb_ti_hsc2: power-monitor@13 {
-		compatible = "ti,lm5066i";
-		reg = <0x13>;
-		shunt-resistor-micro-ohms = <321>;
-	};
-
-	pdb_mps_hsc3: power-monitor@14 {
-		compatible = "mps,mp5926";
-		reg = <0x14>;
-	};
-
-	pdb_ti_hsc3: power-monitor@15 {
-		compatible = "ti,lm5066i";
-		reg = <0x15>;
-		shunt-resistor-micro-ohms = <321>;
-	};
-
-	pdb_mps_hsc4: power-monitor@16 {
-		compatible = "mps,mp5926";
-		reg = <0x16>;
-	};
-
-	pdb_ti_hsc4: power-monitor@17 {
-		compatible = "ti,lm5066i";
-		reg = <0x17>;
-		shunt-resistor-micro-ohms = <500>;
-	};
-
 	pdb_ioexp_20: gpio@20 {
 		compatible = "nxp,pca9555";
 		reg = <0x20>;

---
base-commit: c2b9fc3f7091157518a3ac2282a0a8bc797c227a
change-id: 20260730-upstream-sanmiguel-remove-hsc-nodes-b99c93ec0d9b

Best regards,
--  
Potin Lai <potin.lai.pt@gmail.com>



^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] ARM: dts: aspeed: sanmiguel: Remove HSC nodes
  2026-07-30 13:11 [PATCH] ARM: dts: aspeed: sanmiguel: Remove HSC nodes Potin Lai
@ 2026-07-30 13:17 ` sashiko-bot
  0 siblings, 0 replies; 2+ messages in thread
From: sashiko-bot @ 2026-07-30 13:17 UTC (permalink / raw)
  To: Potin Lai; +Cc: robh, devicetree, conor+dt

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removing actual hardware from the Device Tree to bypass kernel probing for userspace preference violates DT principles.
--

--- Patch [1]: [PATCH] ARM: dts: aspeed: sanmiguel: Remove HSC nodes ---
commit 4baedd7709172e87dfefc81a46cefd1b968b6e6a
Author: Potin Lai <potin.lai.pt@gmail.com>

ARM: dts: aspeed: sanmiguel: Remove HSC nodes

This commit removes Hot-Swap Controller power monitor nodes from the device
tree. The commit message states this is done to prevent automatic kernel
probing and allow userspace to handle the device instantiation.

> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts
> index 3cc6e772cc8c4..98f224d2c091f 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts
> @@ -442,50 +442,6 @@ &i2c8 {
>  &i2c9 {
>  	status = "okay";
>  
> -	pdb_mps_hsc1: power-monitor@10 {
> -		compatible = "mps,mp5926";
> -		reg = <0x10>;
> -	};

[Severity: Medium]
Does removing these nodes to accommodate userspace policy conflict with the
principle that the device tree should be an OS-agnostic description of the
physical hardware?

Since the device tree is meant to describe the physical hardware rather than
dictate software configuration, removing physically present devices to prevent
kernel probing is typically avoided. If these components are on hot-pluggable
boards or are conditionally populated, would it be more appropriate to use
device tree overlays, or to mark the nodes with status = "disabled" instead
of deleting the hardware description outright?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260730-upstream-sanmiguel-remove-hsc-nodes-v1-1-f0308eb8a00c@gmail.com?part=1

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-07-30 13:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-30 13:11 [PATCH] ARM: dts: aspeed: sanmiguel: Remove HSC nodes Potin Lai
2026-07-30 13:17 ` sashiko-bot

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.