From: Yang Chen <yangchen.openbmc@gmail.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
patrick@stwcx.xyz, amithash@meta.com
Cc: Jerry.Lin@quantatw.com, yang.chen@quantatw.com
Subject: [PATCH v1 4/4] ARM: dts: aspeed: minerva: add second source RTC
Date: Thu, 12 Dec 2024 21:32:26 +0800 [thread overview]
Message-ID: <20241212133226.342937-5-yangchen.openbmc@gmail.com> (raw)
In-Reply-To: <20241212133226.342937-1-yangchen.openbmc@gmail.com>
Add second source RTC on i2c bus 9.
Signed-off-by: Yang Chen <yangchen.openbmc@gmail.com>
---
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
index 7fddbe833cc2..ef96b17becb2 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
@@ -1292,6 +1292,11 @@ rtc@51 {
compatible = "nxp,pcf8563";
reg = <0x51>;
};
+
+ rtc@68 {
+ compatible = "dallas,ds1339";
+ reg = <0x68>;
+ };
};
&i2c12 {
--
2.34.1
next prev parent reply other threads:[~2024-12-12 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 13:32 [PATCH v1 0/4] Revise Meta (Facebook) Minerva BMC Yang Chen
2024-12-12 13:32 ` [PATCH v1 1/4] ARM: dts: aspeed: minerva: add i/o expanders on bus 0 Yang Chen
2024-12-12 13:32 ` [PATCH v1 2/4] ARM: dts: aspeed: minerva: add i/o expanders on each FCB Yang Chen
2024-12-12 13:32 ` [PATCH v1 3/4] ARM: dts: aspeed: minerva: add bmc ready led setting Yang Chen
2024-12-12 13:32 ` Yang Chen [this message]
2024-12-13 5:28 ` [PATCH v1 0/4] Revise Meta (Facebook) Minerva BMC Andrew Jeffery
2024-12-13 11:13 ` Krzysztof Kozlowski
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=20241212133226.342937-5-yangchen.openbmc@gmail.com \
--to=yangchen.openbmc@gmail.com \
--cc=Jerry.Lin@quantatw.com \
--cc=amithash@meta.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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+dt@kernel.org \
--cc=yang.chen@quantatw.com \
/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 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.