Merge tag 'u-boot-imx-next-20241126' of https://gitlab.denx.de/u-boot/custodians...

[J-u-boot.git] / doc / I2C_Edge_Conditions

diff --git a/doc/I2C_Edge_Conditions b/doc/I2C_Edge_Conditions
index 44d34785499773dca1d5a38a1297110ea71479e7..9ccb21c5092329c6bc26f7c72974279035daee8e 100644 (file)
--- a/doc/I2C_Edge_Conditions
+++ b/doc/I2C_Edge_Conditions
@@ -31,12 +31,10 @@ Notes
 !!!THIS IS AN UNDOCUMENTED I2C BUS BUG, NOT A AMCC 4xx BUG!!!
 
 This reset edge condition could possibly be present in every I2C
-controller and device available. For boards where a I2C bus reset
-function can be implemented a i2c_init_board() function should be
-provided and enabled by #define'ing CFG_I2C_INIT_BOARD in your
-board's config file. Note that this is NOT necessary when using the
-bit-banging I2C driver (common/soft_i2c.c) as this already includes
-the I2C bus reset sequence.
+controller and device available.
+
+Note that this problem does not happen when using the bit-banging I2C driver
+(common/soft_i2c.c) as this already includes the I2C bus reset sequence.
 
 
 Many thanks to Bill Hunter for finding this serious BUG.