I tested on bf537-stamp board and found the slave address of ad5252 in extend board was 0x2e. The ad5252 has two bits for slave address decode, customers can define the slave address (from 0x2c ... 0x2f) and then the I2C_BOARD_INFO for ad5252.
FYI. http://www.analog.com/static/imported-files/data_sheets/AD5251_5252.pdf On Fri, Oct 22, 2010 at 2:45 PM, Mike Frysinger <[email protected]> wrote: > On Mon, Aug 30, 2010 at 06:51, <[email protected]> wrote: >> Revision 9118 Author steven.miao Date 2010-08-30 06:51:47 -0400 (Mon, 30 Aug >> 2010) >> >> Log Message >> >> [#6197][#6201] twi_lcd: support for bf527-ezkit and bf537-stamp >> >> add ad5252 i2c_board_info for bf527-ezkit and modify i2c address >> of ad5252 for bf537-stamp. >> >> Modified: trunk/arch/blackfin/mach-bf537/boards/stamp.c (9117 => 9118) >> >> @@ -2422,7 +2422,7 @@ >> #endif >> #if defined(CONFIG_BFIN_TWI_LCD) || defined(CONFIG_BFIN_TWI_LCD_MODULE) >> { >> - I2C_BOARD_INFO("ad5252", 0x2f), >> + I2C_BOARD_INFO("ad5252", 0x2e), >> }, >> #endif > > why do we use 0x2f for the slave address on all boards but the bf537-stamp ? > -mike > _______________________________________________ Linux-kernel-commits mailing list [email protected] https://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
