From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
Cc: Guennadi Liakhovetski
<g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: Complex I2C device
Date: Tue, 19 Feb 2008 15:23:48 +0100 [thread overview]
Message-ID: <20080219152348.0cc481d5@hyperion.delvare> (raw)
In-Reply-To: <20080219141049.GD8190-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
On Tue, 19 Feb 2008 15:10:49 +0100, Rodolfo Giometti wrote:
> 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?
Yep, that's exactly the idea.
> It looks *really* good. :)
Credit go to David Brownell.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-02-19 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 14:46 Complex I2C device Rodolfo Giometti
[not found] ` <20080130144657.GA9444-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2008-01-30 20:32 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.0801302126150.6547-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2008-01-31 9:16 ` Rodolfo Giometti
[not found] ` <20080131091619.GI9444-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2008-02-19 13:21 ` Jean Delvare
[not found] ` <20080219142133.2e022910-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-02-19 14:10 ` Rodolfo Giometti
[not found] ` <20080219141049.GD8190-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2008-02-19 14:23 ` Jean Delvare [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080219152348.0cc481d5@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=g.liakhovetski-Mmb7MZpHnFY@public.gmane.org \
--cc=giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox