From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Kevin Tung <kevin.tung.openbmc@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Amithash Prasasd <amithash@meta.com>,
Kevin Tung <Kevin.Tung@quantatw.com>,
Ken Chen <Ken.Chen@quantatw.com>,
Leo Yang <Leo-Yang@quantatw.com>
Subject: Re: [PATCH v3 5/5] ARM: dts: aspeed: yosemite5: Correct power monitor shunt resistor
Date: Thu, 08 Jan 2026 15:52:40 +1030 [thread overview]
Message-ID: <4441e66d607fe442e392b8a82c134adced03a5dc.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251219-yv5_revise_dts-v3-5-ca1d5a382013@gmail.com>
Hi Kevin,
On Fri, 2025-12-19 at 16:09 +0800, Kevin Tung wrote:
> Correct the shunt resistor value in the DTS with the hardware setting
> to ensure accurate power and current measurements.
Why were the existing values wrong? Why are the new values correct? Can
you please add more information here explaining both concerns?
Andrew
next prev parent reply other threads:[~2026-01-08 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 8:09 [PATCH v3 0/5] Revise Meta Yosemite5 devicetree Kevin Tung
2025-12-19 8:09 ` [PATCH v3 1/5] ARM: dts: aspeed: yosemite5: Increase i2c4/i2c12 bus speed to 400 kHz Kevin Tung
2025-12-19 8:09 ` [PATCH v3 2/5] ARM: dts: aspeed: yosemite5: Remove ambiguous power monitor DTS nodes Kevin Tung
2025-12-19 8:09 ` [PATCH v3 3/5] ARM: dts: aspeed: yosemite5: Add new SGPIO line names and rename signal Kevin Tung
2025-12-19 8:09 ` [PATCH v3 4/5] ARM: dts: aspeed: yosemite5: Add ipmb node for OCP debug card Kevin Tung
2025-12-19 8:09 ` [PATCH v3 5/5] ARM: dts: aspeed: yosemite5: Correct power monitor shunt resistor Kevin Tung
2026-01-08 5:22 ` Andrew Jeffery [this message]
2026-01-30 8:33 ` Kevin Tung
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=4441e66d607fe442e392b8a82c134adced03a5dc.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Ken.Chen@quantatw.com \
--cc=Kevin.Tung@quantatw.com \
--cc=Leo-Yang@quantatw.com \
--cc=amithash@meta.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kevin.tung.openbmc@gmail.com \
--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=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
all inboxes | Powered by JetHome®