diff options
Diffstat (limited to 'doc/I2C_Edge_Conditions')
| -rw-r--r-- | doc/I2C_Edge_Conditions | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/I2C_Edge_Conditions b/doc/I2C_Edge_Conditions index 91557a3..be7f1be 100644 --- a/doc/I2C_Edge_Conditions +++ b/doc/I2C_Edge_Conditions @@ -31,8 +31,13 @@ Notes !!!THIS IS AN UNDOCUMENTED I2C BUS BUG, NOT A IBM 4xx BUG!!! This reset edge condition could possibly be present in every I2C -controller and device available. We should probably have a bus reset -function for all our target CPUs. +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. + Many thanks to Bill Hunter for finding this serious BUG. email to: <williamhunter@attbi.com> |