From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Peter Yin <peteryin.openbmc@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/4] ARM: dts: aspeed: harma: add sq52206 power monitor device
Date: Mon, 22 Sep 2025 13:06:12 +0930 [thread overview]
Message-ID: <f76e867ca4dff82744958a8b555cf226139bcd78.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250917101828.2589069-4-peteryin.openbmc@gmail.com>
On Wed, 2025-09-17 at 18:18 +0800, Peter Yin wrote:
> Add the SQ52206 power monitor device and reorder the sequence.
>
> Signed-off-by: Peter Yin <peteryin.openbmc@gmail.com>
> ---
> .../dts/aspeed/aspeed-bmc-facebook-harma.dts | 28 +++++++++++------
> --
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> index bcef91e6eb54..fe72d47a7632 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> @@ -353,14 +353,15 @@ eeprom@52 {
> reg = <0x52>;
> };
>
> - power-monitor@69 {
> - compatible = "pmbus";
> - reg = <0x69>;
> + power-monitor@40 {
> + compatible = "infineon,xdp710";
> + reg = <0x40>;
> };
>
> - temperature-sensor@49 {
> - compatible = "ti,tmp75";
> - reg = <0x49>;
> + power-monitor@41 {
> + compatible = "silergy,sq52206";
> + reg = <0x41>;
> + shunt-resistor = <500>;
> };
>
> power-monitor@44 {
> @@ -369,16 +370,21 @@ power-monitor@44 {
> shunt-resistor-micro-ohms = <250>;
> };
>
> - power-monitor@40 {
> - compatible = "infineon,xdp710";
> - reg = <0x40>;
> - };
> -
> power-monitor@45 {
> compatible = "ti,ina238";
> reg = <0x45>;
> shunt-resistor = <500>;
> };
> +
> + power-monitor@69 {
> + compatible = "pmbus";
I realise you're just moving this node, but I'm surprised it hasn't
caused trouble otherwise. This happens to work due to a quirk of I2C
device IDs in the kernel but it's not a documented compatible.
Compatible strings need to represent the physical device. Can you
please split out a patch either dropping this node, or replacing the
compatible string with something appropriate?
Andrew
next prev parent reply other threads:[~2025-09-22 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 10:18 [PATCH v1 0/4] Revise Meta(Facebook) Harma BMC(AST2600) Peter Yin
2025-09-17 10:18 ` [PATCH v1 1/4] ARM: dts: aspeed: harma: add new line between the child nodes Peter Yin
2025-09-17 10:18 ` [PATCH v1 2/4] ARM: dts: aspeed: harma: use power-monitor instead of power-sensor Peter Yin
2025-09-17 10:18 ` [PATCH v1 3/4] ARM: dts: aspeed: harma: add sq52206 power monitor device Peter Yin
2025-09-22 3:36 ` Andrew Jeffery [this message]
2025-09-24 1:47 ` Peter Yin
2025-09-17 10:18 ` [PATCH v1 4/4] ARM: dts: aspeed: harma: add retimer sgpio Peter Yin
2025-09-22 3:31 ` [PATCH v1 0/4] Revise Meta(Facebook) Harma BMC(AST2600) Andrew Jeffery
2025-09-24 1:00 ` Peter Yin
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=f76e867ca4dff82744958a8b555cf226139bcd78.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peteryin.openbmc@gmail.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