All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 5/6]: i2c: Add bus addressing support.
Date: Wed, 15 Oct 2008 14:37:22 -0700 (PDT)	[thread overview]
Message-ID: <20081015.143722.260594637.davem@davemloft.net> (raw)
In-Reply-To: <20081015145228.14b1ae77-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Date: Wed, 15 Oct 2008 14:52:28 +0200

> Hi David,
> 
> On Thu, 21 Aug 2008 02:43:30 -0700 (PDT), David Miller wrote:
> > 
> > i2c: Add bus addressing support.
> > 
> > Some I2C bus controllers support the driving of multiple I2C bus
> > segments (think PCI domains).
> > 
> > For example, the pcf8584 variants on some sparc64 boxes can do this.
> > They have an auxiliary 8-bit register that specifies the I2C bus each
> > I2C operation acts upon.  In the openfirmware device tree, the I2C
> > client devices are described using an 8-bit bus address and a 10-bit
> > I2C device address.
> 
> Can you please point me to the part of the PCF8454 datasheet which
> explains this? I can't find it. As I read the datasheet, the PCF8454
> supports a single I2C bus.

It's a feature Sun added to their PCF chips.  The register address
is forwarded to an internal MUX they implemented which implements
the register selecting the I2C bus.

> Oh my, holy crap! I can't believe you dared to propose this.

Propose an alternative solution that actually works and preserves
compatability, as mine does.

> I don't like this at all. This really looks like a custom hack to solve
> the problem at hand without paying too much attention to compatibility
> issues which I am certain will arise. Just to mention the first one
> that comes to mind: access from user-space through i2c-dev, and
> specifically i2c-tools.

I got that working, read the patch my patch works, I was careful
to keep things working.

> What makes your setup fundamentally different from a motherboard with
> more than one I2C bus (which is a rather common case)? Why don't you
> simply register one i2c_adapter for each i2c bus segment?

It doesn't work like that.  All the bit banging goes through the
one I2C controller, the bus it is accessing is simply changed behind
it's back by that special register.

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

  parent reply	other threads:[~2008-10-15 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  9:43 [PATCH 5/6]: i2c: Add bus addressing support David Miller
     [not found] ` <20080821.024330.51639001.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-08-21 12:56   ` Peter Korsgaard
2008-10-15 12:52   ` Jean Delvare
     [not found]     ` <20081015145228.14b1ae77-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-10-15 21:37       ` David Miller [this message]
     [not found]         ` <20081015.143722.260594637.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-10-17 15:24           ` Jean Delvare

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=20081015.143722.260594637.davem@davemloft.net \
    --to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.