From: Lucas Stach <l.stach@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
patchwork-lst@pengutronix.de
Subject: [PATCH 02/10] ARM: dts: imx6: RDU2: reduce i2c drive-strength
Date: Mon, 25 Jan 2021 19:47:28 +0100 [thread overview]
Message-ID: <20210125184736.1226435-2-l.stach@pengutronix.de> (raw)
In-Reply-To: <20210125184736.1226435-1-l.stach@pengutronix.de>
The current 25 Ohm drive-strength is much too strong, resulting in
significant overshoot of the signal. Reduce the drive-strength to
75 Ohm to get rid of those issues.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi b/arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi
index 04a66339ceb3..56323890430e 100644
--- a/arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi
@@ -984,22 +984,22 @@
pinctrl_i2c1: i2c1grp {
fsl,pins = <
- MX6QDL_PAD_CSI0_DAT8__I2C1_SDA 0x4001b8b1
- MX6QDL_PAD_CSI0_DAT9__I2C1_SCL 0x4001b8b1
+ MX6QDL_PAD_CSI0_DAT8__I2C1_SDA 0x4001b811
+ MX6QDL_PAD_CSI0_DAT9__I2C1_SCL 0x4001b811
>;
};
pinctrl_i2c2: i2c2grp {
fsl,pins = <
- MX6QDL_PAD_KEY_COL3__I2C2_SCL 0x4001b8b1
- MX6QDL_PAD_KEY_ROW3__I2C2_SDA 0x4001b8b1
+ MX6QDL_PAD_KEY_COL3__I2C2_SCL 0x4001b811
+ MX6QDL_PAD_KEY_ROW3__I2C2_SDA 0x4001b811
>;
};
pinctrl_i2c3: i2c3grp {
fsl,pins = <
- MX6QDL_PAD_GPIO_3__I2C3_SCL 0x4001b8b1
- MX6QDL_PAD_GPIO_6__I2C3_SDA 0x4001b8b1
+ MX6QDL_PAD_GPIO_3__I2C3_SCL 0x4001b811
+ MX6QDL_PAD_GPIO_6__I2C3_SDA 0x4001b811
>;
};
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-25 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 18:47 [PATCH 01/10] ARM: dts: imx6: rdu2: enable WDOG1 Lucas Stach
2021-01-25 18:47 ` Lucas Stach [this message]
2021-01-25 18:47 ` [PATCH 03/10] ARM: dts: imx6: RDU2: enable RMI4 reduced reporting Lucas Stach
2021-01-25 18:47 ` [PATCH 04/10] ARM: dts: imx6: RDU2: only trigger IRQ on falling edge ucs1002 ALERT pin Lucas Stach
2021-01-25 18:47 ` [PATCH 05/10] ARM: dts: imx6: RDU2: adjust audio devices nomenclature Lucas Stach
2021-01-25 18:47 ` [PATCH 06/10] arm64: dts: zii-ultra: add sound support Lucas Stach
2021-01-25 18:47 ` [PATCH 07/10] arm64: dts: zii-ultra: fix i2c pin configuration Lucas Stach
2021-01-25 18:47 ` [PATCH 08/10] arm64: dts: zii-ultra: limit USB ports to USB2 speed Lucas Stach
2021-01-25 18:47 ` [PATCH 09/10] arm64: dts: zii-ultra: only trigger IRQ on falling edge ucs1002 ALERT pin Lucas Stach
2021-01-25 18:47 ` [PATCH 10/10] arm64: dts: zii-rmb3: enable RMI4 reduced reporting Lucas Stach
2021-01-30 13:55 ` [PATCH 01/10] ARM: dts: imx6: rdu2: enable WDOG1 Shawn Guo
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=20210125184736.1226435-2-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=patchwork-lst@pengutronix.de \
--cc=shawnguo@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).