Skip to contentSkip to conversation

cm-t35: add I2C multi-bus support

PATCH New Igor Grinberg 2 participants 7 messages Apr 2, 2012 – Apr 23, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 cm-t35: add I2C multi-bus support

From: Nikita Kiryanov <[email protected]>

Enable I2C multi-bus support and config I2C muxes for I2C2 and I2C3.

---
 board/cm_t35/cm_t35.c    |    6 ++++++
 include/configs/cm_t35.h |    1 +
 2 files changed, 7 insertions(+), 0 deletions(-)
board/cm_t35/cm_t35.c +6 -0
index 0a04994..bc991c4 100644
@@ -241,6 +241,12 @@ static void cm_t3x_set_common_muxconf(void)
 	/* I2C1 */
 	MUX_VAL(CP(I2C1_SCL),		(IEN  | PTU | EN  | M0)); /*I2C1_SCL*/
 	MUX_VAL(CP(I2C1_SDA),		(IEN  | PTU | EN  | M0)); /*I2C1_SDA*/
+	/* I2C2 */
+	MUX_VAL(CP(I2C2_SCL),		(IEN  | PTU | EN  | M0)); /*I2C2_SCL*/
+	MUX_VAL(CP(I2C2_SDA),		(IEN  | PTU | EN  | M0)); /*I2C2_SDA*/
+	/* I2C3 */
+	MUX_VAL(CP(I2C3_SCL),		(IEN  | PTU | EN  | M0)); /*I2C3_SCL*/
+	MUX_VAL(CP(I2C3_SDA),		(IEN  | PTU | EN  | M0)); /*I2C3_SDA*/
 
 	/* control and debug */
 	MUX_VAL(CP(SYS_32K),		(IEN  | PTD | DIS | M0)); /*SYS_32K*/
include/configs/cm_t35.h +1 -0
index fe91c10..b28bd8e 100644
@@ -156,6 +156,7 @@
 #define CONFIG_DRIVER_OMAP34XX_I2C
 #define CONFIG_SYS_I2C_EEPROM_ADDR	0x50
 #define CONFIG_SYS_I2C_EEPROM_ADDR_LEN	1
+#define CONFIG_I2C_MULTI_BUS
 
 /*
  * TWL4030
Signature · 1 line
1.7.3.4
#2 lore raw

PATCH 1/1 cm-t35: add I2C multi-bus support

Hi Tom,

Quoted 9 lines · Tom Rini
Quoted 6 lines · Igor Grinberg

From: Nikita Kiryanov<[email protected]>

Enable I2C multi-bus support and config I2C muxes for I2C2 and I2C3.

Have you confirmed this is sufficient and there's no changes required in omap24xx_i2c.c ? Thanks!

I don't know what do you mean by sufficient...
I've tested this patch on bus 0 and 2 by reading/writing to eeproms and it is working fine, so IMO it is sufficient.

Some time ago, I've seen a problem with Ethernet initialization and tracked it down to:
0607e2b ARMV7: OMAP: Write more than 1 byte at a time in i2c_write

cm-t35 and cm-t3730 have Ethernet reset signal wired to TPS65930 GPIO, so I2C transaction is needed to reset the Ethernet.

So my conclusion was that the commit above changed the timings and that broke the Ethernet reset code.

After examining the Ethernet reset code, the fix was obvious, as the reset code had wrong timing for the reset pulse. So I've fixed this locally, but forgot to send a patch. Sending in a moment...

Signature · 2 lines
Regards,
Igor.
#3 lore raw

PATCH 1/1 cm-t35: add I2C multi-bus support

In reply to Igor Grinberg
Quoted 6 lines · Igor Grinberg

From: Nikita Kiryanov <[email protected]>

Enable I2C multi-bus support and config I2C muxes for I2C2 and I2C3.

Queued up for u-boot-ti/next (which I intend to PR Friday).

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120403/da277125/attachment.pgp>
#5 lore raw

PATCH 1/1 cm-t35: add I2C multi-bus support

Hi Tom,

Quoted 9 lines · Tom Rini
Quoted 6 lines · Igor Grinberg

From: Nikita Kiryanov <[email protected]>

Enable I2C multi-bus support and config I2C muxes for I2C2 and I2C3.

Applied to u-boot-ti/next (and this missed the PR I just sent, sorry).

Hmmm...
Will you send another pull request in some time during the merge window, so it will still reach the v2012.07?

Signature · 2 lines
Regards,
Igor.
#6 lore raw

PATCH 1/1 cm-t35: add I2C multi-bus support

Quoted 8 lines · Igor Grinberg

Hi Tom,

Quoted 5 lines · Tom Rini
Quoted 4 lines · Igor Grinberg

From: Nikita Kiryanov<[email protected]>

Enable I2C multi-bus support and config I2C muxes for I2C2 and I2C3.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

Applied to u-boot-ti/next (and this missed the PR I just sent, sorry).

Hmmm...
Will you send another pull request in some time during the merge window, so it will still reach the v2012.07?

Absolutely.

Signature · 1 line
Tom