Re: Complex I2C device

[Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1466 bytes --]

On Tue, Feb 19, 2008 at 02:21:33PM +0100, Jean Delvare wrote:
> 
> Guennadi's solution (based on David Brownell's work) is actually pretty
> generic as far as GPIOs are concerned. I like it.

If I well understand it I should use i2c_new_dummy() to simply create
an handler for the alternate address.

> > 
> > 
> >                  +---------+
> >            --+---+ Battery |
> >              |   | Manager |
> >              |   +---------+
> >  Bus I2C ->> |
> >              |
> >              |
> >              |   +---------+
> >              +---+         |
> >                  |  CHIP   |
> >                  +---------+
> > 
> > A (complex) battery pack are managed by a "battery manager" and a
> > custom chip connected by the I2C bus (my hardware designer _loves_ I2C
> > bus :). Even these devices can be logically considered as only one
> > (big) battery...
> > 

In this situation into the driver of the «main» device (the battery
manager) I can use i2c_new_dummy() to get an handler to manage the
other I2C chip. Is that right?

It looks *really* good. :)

Rodolfo

-- 

GNU/Linux Solutions                  e-mail:    giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org
Linux Device Driver                             giometti-kaDoWcXyVrEAvxtiuMwx3w@public.gmane.org
Embedded Systems                     		giometti-k2GhghHVRtY@public.gmane.org
UNIX programming                     phone:     +39 349 2432127

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c