From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schweigstill Date: Mon, 15 May 2006 16:43:09 +0200 Subject: [U-Boot-Users] Using a second I2C interface In-Reply-To: <20060512190133.538D8352B0C@atlas.denx.de> References: <20060512190133.538D8352B0C@atlas.denx.de> Message-ID: <4468937D.5000109@schweigstill.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello! Wolfgang Denk schrieb: > A clean design should allow to switch I2C busses usign a command; > additionally, I think we should try to stay backward-compatible with > the existing code. Eventually this is not too difficult: similar to > the "ide" or "usb" commands we could create a new command "i2c > device" which takes as argument the number of the I2C bus which shal > become the current (= active) bus. Then all existing I2C related > commands can be left unchanged (and "i2c device" without arguments > should of course print the ID of the current bus). It has to be taken into account that the I2C busses may have different adress length. So either the address length has to be read back from the low-level driver or a table has to be maintained in the I2C command implementations. With best regards Andreas Schweigstill PS.: Has anybody written some "high-level" I2C commands for chipcard interfaces? -- Dipl.-Phys. Andreas Schweigstill Schweigstill IT | Embedded Systems Schauenburgerstra?e 116, D-24118 Kiel, Germany Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436 Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/