[U-Boot] [PATCH 0/3] Bring in new I2C framework

Tom Rini trini at ti.com
Tue Oct 30 23:38:33 CET 2012


On Mon, Oct 29, 2012 at 10:53:10AM +0100, Heiko Schocher wrote:
> Hello Tom,
> 
> On 26.10.2012 20:44, Tom Rini wrote:
> >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 :)
> 
> As I wrote to simon, stephen, this is an independent problem from the
> new framework patches!

OK.  I was hoping we could just:
- Change init_func_i2c (for ARM/m68k/ppc/nds32, equiv elsewhere) to init
  all configured busses.
- Change the CLI part to track what bus it is operating on.

It sounds like it's more work than just this, really.  Since there is
agreement to push things further after this update, yes, OK, we can go
one step at a time here.  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121030/30eda42a/attachment.pgp>


More information about the U-Boot mailing list