diff options
Diffstat (limited to 'target/linux/mvebu/patches-4.14/413-ARM-dts-armada388-clearfog-increase-speed-of-i2c0-to.patch')
| -rw-r--r-- | target/linux/mvebu/patches-4.14/413-ARM-dts-armada388-clearfog-increase-speed-of-i2c0-to.patch | 42 |
1 files changed, 0 insertions, 42 deletions
diff --git a/target/linux/mvebu/patches-4.14/413-ARM-dts-armada388-clearfog-increase-speed-of-i2c0-to.patch b/target/linux/mvebu/patches-4.14/413-ARM-dts-armada388-clearfog-increase-speed-of-i2c0-to.patch deleted file mode 100644 index 4aedc82fe7..0000000000 --- a/target/linux/mvebu/patches-4.14/413-ARM-dts-armada388-clearfog-increase-speed-of-i2c0-to.patch +++ /dev/null @@ -1,42 +0,0 @@ -From 6e127081e669cf163a818dc04d590790e4ed9527 Mon Sep 17 00:00:00 2001 -From: Russell King <rmk+kernel@armlinux.org.uk> -Date: Tue, 29 Nov 2016 20:06:44 +0000 -Subject: ARM: dts: armada388-clearfog: increase speed of i2c0 to 400kHz - -All the devices on I2C0 support fast mode, so increase the bus speed -to match. The Armada 388 is known to have a timing issue when in -standard mode, which we believe causes the ficticious device at 0x64 -to appear. - -Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> ---- - arch/arm/boot/dts/armada-388-clearfog.dtsi | 7 ++----- - 1 file changed, 2 insertions(+), 5 deletions(-) - ---- a/arch/arm/boot/dts/armada-388-clearfog.dtsi -+++ b/arch/arm/boot/dts/armada-388-clearfog.dtsi -@@ -143,8 +143,7 @@ - }; - - &i2c0 { -- /* Is there anything on this? */ -- clock-frequency = <100000>; -+ clock-frequency = <400000>; - pinctrl-0 = <&i2c0_pins>; - pinctrl-names = "default"; - status = "okay"; -@@ -239,13 +238,11 @@ - }; - }; - -- /* The MCP3021 is 100kHz clock only */ -+ /* The MCP3021 supports standard and fast modes */ - mikrobus_adc: mcp3021@4c { - compatible = "microchip,mcp3021"; - reg = <0x4c>; - }; -- -- /* Also something at 0x64 */ - }; - - &i2c1 { |