From: Chanh Nguyen <chanh@os.amperecomputing.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Chanh Nguyen <chanh@os.amperecomputing.com>
Subject: [PATCH v2 3/3] ARM: dts: aspeed: mtmitchell: Add MCTP
Date: Fri, 19 May 2023 15:52:00 +0700 [thread overview]
Message-ID: <20230519085200.22020-4-chanh@os.amperecomputing.com> (raw)
In-Reply-To: <20230519085200.22020-1-chanh@os.amperecomputing.com>
Enable MCTP driver on I2C3 bus for MCTP transaction
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
---
Changes in v2:
- Update reg for mctp node. [Andrew]
---
arch/arm/boot/dts/aspeed-bmc-ampere-mtmitchell.dts | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-ampere-mtmitchell.dts b/arch/arm/boot/dts/aspeed-bmc-ampere-mtmitchell.dts
index d3c7e7c0fd25..c0316c198a88 100644
--- a/arch/arm/boot/dts/aspeed-bmc-ampere-mtmitchell.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-ampere-mtmitchell.dts
@@ -366,6 +366,13 @@
&i2c3 {
status = "okay";
+ bus-frequency = <1000000>;
+ multi-master;
+ mctp-controller;
+ mctp@10 {
+ compatible = "mctp-i2c-controller";
+ reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
+ };
};
&i2c4 {
--
2.17.1
next prev parent reply other threads:[~2023-05-19 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 8:51 [PATCH v2 0/3] Update the device tree for Ampere's Mt.Mitchell BMC Chanh Nguyen
2023-05-19 8:51 ` [PATCH v2 1/3] ARM: dts: aspeed: mtmitchell: Enable the BMC UART8 and UART9 Chanh Nguyen
2023-05-19 8:51 ` [PATCH v2 2/3] ARM: dts: aspeed: mtmitchell: Update ADC sensors for Mt.Mitchell DVT systems Chanh Nguyen
2023-05-19 8:52 ` Chanh Nguyen [this message]
2023-05-19 13:46 ` [PATCH v2 3/3] ARM: dts: aspeed: mtmitchell: Add MCTP kernel test robot
2023-05-23 22:40 ` kernel test robot
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=20230519085200.22020-4-chanh@os.amperecomputing.com \
--to=chanh@os.amperecomputing.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--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=openbmc@lists.ozlabs.org \
--cc=robh+dt@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