linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
Cc: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Q: I2C multiplexer support
Date: Mon, 7 Dec 2009 13:01:32 +0100	[thread overview]
Message-ID: <20091207130132.621ead05@hyperion.delvare> (raw)
In-Reply-To: <20091207095624.GC3647-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>

On Mon, 7 Dec 2009 10:56:24 +0100, Rodolfo Giometti wrote:
> On Mon, Dec 07, 2009 at 10:07:54AM +0100, Michael Lawnick wrote:
> > Hi,
> > 
> > on my current project I'm now at the point to have to implement
> > multiplexer support. The last patch set from Rodolfo was for 2.6.29,
> > most parts seem to have been integrated already in 2.6.31
> > If I got it correctly the patch based on creating a mux folder with
> > i2c-mux.c as a core file and then additional mux layer files.
> > So my questions:
> > Rodolfo, do you have a more resent patch set?
> 
> No.
> 
> > Jean, what are your plans about multiplexer support, where do you see
> > open issues? Do you agree with current centralized layout or would you
> > prefer independent single files integrating all necessary parts and
> > residing in bus folder?
> 
> If Jean agree on my last rework I'm willing to do all whatever is
> needed in order to finish this job and integrate this support into the
> main line. :)

I can't tell if I agree without reading the code, and I won't read the
code if the patches do not apply. But don't worry anyway: I do want to
add multiplexing support, so even if not in the exact form you're
proposing, your work will definitely be the starting point for whatever
we end up agreeing on. Which means that your forward porting work will
not be time wasted, whatever happens next.

Anyway I don't expect the forward porting to need too much work.

-- 
Jean Delvare

      parent reply	other threads:[~2009-12-07 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  9:07 Q: I2C multiplexer support Michael Lawnick
     [not found] ` <4B1CC5EA.7040902-Mmb7MZpHnFY@public.gmane.org>
2009-12-07  9:51   ` Jean Delvare
     [not found]     ` <20091207105132.6926bf19-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-12-07 10:00       ` Rodolfo Giometti
     [not found]         ` <20091207100000.GD3647-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2009-12-07 11:37           ` Michael Lawnick
2009-12-07 11:57           ` Jean Delvare
     [not found]             ` <20091207125737.3da7bd3b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-12-07 14:21               ` Rodolfo Giometti
2009-12-07  9:56   ` Rodolfo Giometti
     [not found]     ` <20091207095624.GC3647-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
2009-12-07 12:01       ` 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=20091207130132.621ead05@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ml.lawnick-Mmb7MZpHnFY@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).