linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
To: Joe Ghalam <joe.ghalam-h+EFgaI/KG7uufBYgWm87A@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2c Mux support for LTC4306 multiplexers
Date: Thu, 2 Sep 2010 10:07:08 +0200	[thread overview]
Message-ID: <20100902080708.GC28869@enneenne.com> (raw)
In-Reply-To: <4C7ECF6D.30602-h+EFgaI/KG7uufBYgWm87A@public.gmane.org>

On Wed, Sep 01, 2010 at 03:10:53PM -0700, Joe Ghalam wrote:
>    Hi,
>    I have been trying to include you i2c changes to bring in support for the
>    i2c muxes in my system. I'm using Linux 2.6.33.2 with an MPC8547E. There
>    are two IC2 buses hanging off the host processor. The 2nd I2C bus has 3
>    LT4306 multiplexers (4 ch per device).
> 
>    My current setup (without the i2c-mux) uses the buses/i2c-mpc.c to create
>    two adapters mapped to /dev/i2c-0 and /dev/i2c-1 (these devices are
>    services by an i2c proxy). I would like to move away from this setup by
>    using i2c-mux + mux specific drivers.
> 
>    I have ported your changes in my version of Linux as best as I could, and
>    I also used pca542x related files as templates to create support for
>    ltc4306. During the system boot up, as usual, I see two "MPC adapter"
>    adapters, 0 and 1, getting registered, and I also see my LTC4306 device
>    registered. But I haven't been able to change the i2c-mpc to probe the
>    already discovered buses for any muxes.

Maybe you should provide some code and/or debugging messages... I'm
sorry but I don't understand your problem.

Ciao,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail: giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org
Linux Device Driver                          giometti-k2GhghHVRtY@public.gmane.org
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it

       reply	other threads:[~2010-09-02  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C7ECF6D.30602@cyanoptics.com>
     [not found] ` <4C7ECF6D.30602-h+EFgaI/KG7uufBYgWm87A@public.gmane.org>
2010-09-02  8:07   ` Rodolfo Giometti [this message]
     [not found]     ` <20100902080708.GC28869-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2010-09-02 10:48       ` i2c Mux support for LTC4306 multiplexers Michael Lawnick
     [not found]         ` <4C7F80FF.5050005-Mmb7MZpHnFY@public.gmane.org>
2010-09-02 12:02           ` 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=20100902080708.GC28869@enneenne.com \
    --to=giometti-avvdyk/kqijwk0htik3j/w@public.gmane.org \
    --cc=joe.ghalam-h+EFgaI/KG7uufBYgWm87A@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).