From: Ninad Palsule <ninad@linux.ibm.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
eajames@linux.ibm.com
Cc: Ninad Palsule <ninad@linux.ibm.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 1/3] ARM: dts: aspeed: system1: Bump up i2c busses freq
Date: Tue, 1 Oct 2024 14:17:48 -0500 [thread overview]
Message-ID: <20241001191756.234096-2-ninad@linux.ibm.com> (raw)
In-Reply-To: <20241001191756.234096-1-ninad@linux.ibm.com>
Bump up i2c8 and i2c15 bus frequency so that PCIe slot and FPGA runs
faster
Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
---
arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts | 2 ++
1 file changed, 2 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 f3efecc7eb8d0..1cbf257fb0a0b 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts
@@ -1007,6 +1007,7 @@ i2c7mux0chn7: i2c@7 {
&i2c8 {
status = "okay";
+ bus-frequency = <400000>;
i2c-mux@71 {
compatible = "nxp,pca9548";
@@ -1468,6 +1469,7 @@ i2c14mux0chn7: i2c@7 {
&i2c15 {
status = "okay";
+ bus-frequency = <400000>;
i2c-mux@71 {
compatible = "nxp,pca9548";
--
2.43.0
next prev parent reply other threads:[~2024-10-01 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:17 [PATCH v1 0/3] Device tree changes for system1 BMC Ninad Palsule
2024-10-01 19:17 ` Ninad Palsule [this message]
2024-10-01 20:48 ` [PATCH v1 1/3] ARM: dts: aspeed: system1: Bump up i2c busses freq Eddie James
2024-10-01 19:17 ` [PATCH v1 2/3] ARM: dts: aspeed: system1: Enable serial gpio0 Ninad Palsule
2024-10-01 20:49 ` Eddie James
2024-10-01 19:17 ` [PATCH v1 3/3] ARM: dts: aspeed: system1: Add GPIO line names Ninad Palsule
2024-10-01 20:50 ` Eddie James
2024-10-02 0:26 ` [PATCH v1 0/3] Device tree changes for system1 BMC Andrew Jeffery
2024-10-02 3:12 ` Ninad Palsule
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=20241001191756.234096-2-ninad@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--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=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).