[U-Boot-Users] [Patch 0/9] U-boot-V2: Introduce I2C support for SDP3430

Robert Schwebel r.schwebel at pengutronix.de
Wed Jun 18 22:44:07 CEST 2008


On Wed, Jun 18, 2008 at 03:21:02PM -0500, Menon, Nishanth wrote:
> > - Please don't bring in things which are not part of the current code
> >   base. If you add code for subsystems, the subsystems must be there
> >   first and *then* their users. Otherwhise we bloat the codebase and we
> >   disable the possibility to add *real* support for PCI, USB and S390
> >   later :-)
>
> Acked. Yep will redo that :).

Yea, looking forward especially for PCI patches :-)

> > Which part of i2c do we actually *need* in the bootloader? What's
> > *your* use case?
>
> I need i2c_transfer -yes - I can customize the changes just for that.
> I do like i2c_transfers, adapters, clients etc.. my immediate need is
> rather simple -> i2c_transfers.

Ok, so let's start with that.

> > I assume we need i2c host controllers, that's quite clear. We also need
> > an abstraction for i2c devices. The only devices I have seen which
> > really needed a bootloader driver are
> >
> > a) eeproms
> > b) RTCs
> > c) analog/digital in/outputs (i.e. gpio expanders)
> >
> > Other use cases?
>
> USB Transceivers, power management devices.

Yes, but I think what we most of all need is the i2c communication with
the device. We should think about if the abstraction of the devices
*behind* the bus brings us anything; note that you can do lots of things
in scripts in u-boot-v2. Linke writing a shell function for your usb
transceivers which just encapsulates the right predefined i2c_read/write
operations.

> Are we ok with i2ctools movement here?

Hmm? How do you mean that?

rsc
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9





More information about the U-Boot mailing list