From: Ninad Palsule <ninad@linux.ibm.com>
To: brgl@bgdev.pl, linus.walleij@linaro.org, minyard@acm.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
openipmi-developer@lists.sourceforge.net, netdev@vger.kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, eajames@linux.ibm.com,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Ninad Palsule <ninad@linux.ibm.com>
Subject: [PATCH v7 3/9] ARM: dts: aspeed: system1: Add IPMB device
Date: Mon, 3 Feb 2025 08:44:13 -0600 [thread overview]
Message-ID: <20250203144422.269948-4-ninad@linux.ibm.com> (raw)
In-Reply-To: <20250203144422.269948-1-ninad@linux.ibm.com>
Add IPMB device sitting behind PCH module
Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
---
arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
index 8f77bc9e860c..0d16987cfc80 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
@@ -763,6 +763,15 @@ i2c3mux0chn7: i2c@7 {
&i2c4 {
status = "okay";
+ multi-master;
+ bus-frequency = <1000000>;
+
+ ipmb@10 {
+ compatible = "ipmb-dev";
+ reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
+
+ i2c-protocol;
+ };
};
&i2c5 {
--
2.43.0
next prev parent reply other threads:[~2025-02-03 14:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 14:44 [PATCH v7 0/9] DTS updates for system1 BMC Ninad Palsule
2025-02-03 14:44 ` [PATCH v7 1/9] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-02-03 15:00 ` Krzysztof Kozlowski
2025-02-03 15:17 ` Ninad Palsule
2025-02-03 16:01 ` Krzysztof Kozlowski
2025-02-03 14:44 ` [PATCH v7 2/9] dt-bindings: gpio: ast2400-gpio: Add hogs parsing Ninad Palsule
2025-02-13 11:30 ` Linus Walleij
2025-02-03 14:44 ` Ninad Palsule [this message]
2025-02-03 14:44 ` [PATCH v7 4/9] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-02-03 14:44 ` [PATCH v7 5/9] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-02-03 14:44 ` [PATCH v7 6/9] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-02-03 14:44 ` [PATCH v7 7/9] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-02-03 14:44 ` [PATCH v7 8/9] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-02-03 14:44 ` [PATCH v7 9/9] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-02-03 15:37 ` [PATCH v7 0/9] DTS updates for system1 BMC Rob Herring (Arm)
2025-02-04 4:33 ` Andrew Jeffery
2025-02-04 19:40 ` Ninad Palsule
2025-02-05 0:05 ` 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=20250203144422.269948-4-ninad@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).