linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peter Yin <peteryin.openbmc@gmail.com>
To: patrick@stwcx.xyz, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/7] ARM: dts: aspeed: Harma: add VR device
Date: Thu, 13 Jun 2024 23:24:20 +0800	[thread overview]
Message-ID: <20240613152425.1582059-3-peteryin.openbmc@gmail.com> (raw)
In-Reply-To: <20240613152425.1582059-1-peteryin.openbmc@gmail.com>

Add isl69260, xdpe152c4 device

Signed-off-by: Peter Yin <peteryin.openbmc@gmail.com>
---
 .../dts/aspeed/aspeed-bmc-facebook-harma.dts  | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)

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 0d349ce1f3e6..ef5ffe190445 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
@@ -398,6 +398,30 @@ imux28: i2c@0 {
 			#address-cells = <1>;
 			#size-cells = <0>;
 			reg = <0>;
+			power-monitor@61 {
+				compatible = "isil,isl69260";
+				reg = <0x61>;
+			};
+			power-monitor@62 {
+				compatible = "isil,isl69260";
+				reg = <0x62>;
+			};
+			power-monitor@63 {
+				compatible = "isil,isl69260";
+				reg = <0x61>;
+			};
+			power-monitor@64 {
+				compatible = "infineon,xdpe152c4";
+				reg = <0x64>;
+			};
+			power-monitor@66 {
+				compatible = "infineon,xdpe152c4";
+				reg = <0x66>;
+			};
+			power-monitor@68 {
+				compatible = "infineon,xdpe152c4";
+				reg = <0x68>;
+			};
 		};
 		imux29: i2c@1 {
 			#address-cells = <1>;
-- 
2.25.1



  parent reply	other threads:[~2024-06-13 15:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 15:24 [PATCH v1 0/7] Revise Meta(Facebook) Harma BMC(AST2600) Peter Yin
2024-06-13 15:24 ` [PATCH v1 1/7] ARM: dts: aspeed: Harma: revise hsc chip Peter Yin
2024-06-13 15:24 ` Peter Yin [this message]
2024-06-16 20:04   ` [PATCH v1 2/7] ARM: dts: aspeed: Harma: add VR device kernel test robot
2024-06-13 15:24 ` [PATCH v1 3/7] ARM: dts: aspeed: Harma: add sgpio name Peter Yin
2024-06-13 15:24 ` [PATCH v1 4/7] ARM: dts: aspeed: Harma: add ina238 Peter Yin
2024-06-13 15:24 ` [PATCH v1 5/7] ARM: dts: aspeed: Harma: add power monitor xdp710 Peter Yin
2024-06-13 15:24 ` [PATCH v1 6/7] ARM: dts: aspeed: Harma: remove multi-host property Peter Yin
2024-06-17 19:18   ` kernel test robot
2024-06-17 23:50     ` Andrew Jeffery
2024-06-13 15:24 ` [PATCH v1 7/7] ARM: dts: aspeed: Harma: remove pca9546 Peter Yin
2024-06-17  7:41   ` Andrew Jeffery

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=20240613152425.1582059-3-peteryin.openbmc@gmail.com \
    --to=peteryin.openbmc@gmail.com \
    --cc=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=patrick@stwcx.xyz \
    --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;
as well as URLs for NNTP newsgroup(s).