linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	giometti-k2GhghHVRtY@public.gmane.org
Subject: Re: Q: I2C multiplexer support
Date: Mon, 7 Dec 2009 10:51:32 +0100	[thread overview]
Message-ID: <20091207105132.6926bf19@hyperion.delvare> (raw)
In-Reply-To: <4B1CC5EA.7040902-Mmb7MZpHnFY@public.gmane.org>

Hi Michael,

On Mon, 07 Dec 2009 10:07:54 +0100, Michael Lawnick wrote:
> 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,

Correct.

> most parts seem to have been integrated already in 2.6.31

I don't think so, no. What went in (or more exactly, out of) i2c-core
in 2.6.31 was the removal of the legacy i2c binding model, along with
the cleanups that allowed. It should make multiplexing support easier
to add, but that's about it.

> 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?

I've been asking the same some weeks ago.

> Jean, what are your plans about multiplexer support, where do you see
> open issues?

In all honesty, I did not look at Rodolfo's code at all. When he sent
it originally, I didn't have the time, being in the middle of major
i2c-core changes and cleanups. After 2.6.31 was released, I finally had
the time to look into it. But as I knew the recent i2c-core changes
would require Rodolfo's patches to be rebased, I asked him to do that
first. But now it's apparently Rodolfo's time to be busy :( If you want
to help, you're welcome.

> Do you agree with current centralized layout or would you
> prefer independent single files integrating all necessary parts and
> residing in bus folder?

Not having looked at the current proposal, I can't really comment on
the design. But having a separate folder for mux drivers sounds sane at
first sight.

-- 
Jean Delvare

  parent reply	other threads:[~2009-12-07  9:51 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 [this message]
     [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

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=20091207105132.6926bf19@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=giometti-k2GhghHVRtY@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).