From: Andrew Jeffery <andrew@codeconstruct•com.au>
To: Daniel Hsu <d486250@gmail•com>
Cc: robh@kernel•org, krzk+dt@kernel•org, conor+dt@kernel•org,
joel@jms•id.au, devicetree@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-aspeed@lists•ozlabs.org, linux-kernel@vger•kernel.org,
Daniel Hsu <Daniel-Hsu@quantatw•com>
Subject: Re: [PATCH v2] ARM: dts: aspeed: yosemite5: Add MP5998 power monitor
Date: Mon, 18 May 2026 22:14:42 +0930 [thread overview]
Message-ID: <64ab943e8874bd5ef22c0f1a19b7d89daea83a9e.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260331120734.39260-1-Daniel-Hsu@quantatw.com>
Hi Daniel,
On Tue, 2026-03-31 at 20:07 +0800, Daniel Hsu wrote:
> Add an MP5998 power monitor used to monitor the power consumption
> of the Paddle_P12V_HSC rail on the Yosemite5 paddle board.
>
> [v2]
> - Describe the purpose of the power monitor
> - Remove software/driver related description
>
> Signed-off-by: Daniel Hsu <Daniel-Hsu@quantatw•com>
I've applied this to the BMC tree. However, in the future, the
changelog for the series should go underneath '---' below, so it's not
included in the commit message when the patch is applied.
Andrew
> ---
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts
> index 2486981f3d6b..6287f80d70d9 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite5.dts
> @@ -422,6 +422,11 @@ power-sensor@45 {
> shunt-resistor = <1000>;
> };
>
> + power-monitor@46 {
> + compatible = "mps,mp5998";
> + reg = <0x46>;
> + };
> +
> power-monitor@47 {
> compatible = "ti,tps25990";
> reg = <0x47>;
prev parent reply other threads:[~2026-05-18 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 12:07 [PATCH v2] ARM: dts: aspeed: yosemite5: Add MP5998 power monitor Daniel Hsu
2026-05-18 12:44 ` Andrew Jeffery [this message]
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=64ab943e8874bd5ef22c0f1a19b7d89daea83a9e.camel@codeconstruct.com.au \
--to=andrew@codeconstruct$(echo .)com.au \
--cc=Daniel-Hsu@quantatw$(echo .)com \
--cc=conor+dt@kernel$(echo .)org \
--cc=d486250@gmail$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=joel@jms$(echo .)id.au \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-aspeed@lists$(echo .)ozlabs.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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