From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 26 Oct 2012 11:44:45 -0700 Subject: [U-Boot] [PATCH 0/3] Bring in new I2C framework In-Reply-To: References: <1350927621-12481-1-git-send-email-hs@denx.de> Message-ID: <20121026184445.GF31793@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Oct 25, 2012 at 02:37:08PM -0700, Simon Glass wrote: [snip] > Later, I wonder whether the concept of a 'current' i2c bus should be > maintained by the command line interpreter, rather than the i2c > system. Because to be honest, most of the drivers I see have to save > the current bus number, set the current bus, do the operation, then > set the bus back how they found it (to preserve whatever the user > things is the current bus). I agree. Lets move the notion of "current" to cmd_i2c and make everything internally pass around the bus to operate on. Or try going down this path and find a fatal problem :) -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: