All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
To: Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c: add generic I2C multiplexer using gpio api
Date: Tue, 20 Jul 2010 13:51:50 +0200	[thread overview]
Message-ID: <4C458DD6.2020306@gmx.de> (raw)
In-Reply-To: <87y6d6ie7q.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>

Peter Korsgaard said the following:
>>>>>> "Michael" == Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org> writes:
> 
>  >> But this patch is independent from that work as the mux access isn't
>  >> through I2C, hence no changes to i2c-core needed.
> 
>  Michael> i2c-mux patch does not expect path control via i2c.
>  Michael> Your scenario fits perfectly.
> 
> Hmm, I'll take a closer look at the last version then - sorry. In the
> past it afaik did. What is the point of the i2c-core changes if path
> control isn't via i2c?
> 
The changes in i2c-core are mostly for traversing the tree and check for
duplicate addresses.
>From i2c-core and user space view there is no logical difference between
a h/w adapter and a multiplexer. They are all handled the same.
But I fear your question arises from your different approach. May be it
gets more clear after looking into i2c-mux.c and pca954x.c.

-- 
KR
Michael Lawnick

      parent reply	other threads:[~2010-07-20 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-04 23:19 [PATCH] i2c: add generic I2C multiplexer using gpio api Peter Korsgaard
     [not found] ` <1278285584-13632-1-git-send-email-peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@public.gmane.org>
2010-07-20  9:13   ` Peter Korsgaard
     [not found]     ` <87fwzejz1v.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2010-07-20  9:50       ` Jean Delvare
     [not found]         ` <20100720115005.3b3fa865-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-07-20  9:58           ` Peter Korsgaard
     [not found]             ` <87bpa2jwzy.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2010-07-20 11:04               ` Jean Delvare
     [not found]                 ` <20100720130417.5be0bb51-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-07-20 11:27                   ` Peter Korsgaard
2010-07-20 11:09               ` Michael Lawnick
     [not found]                 ` <4C4583F3.8080807-Mmb7MZpHnFY@public.gmane.org>
2010-07-20 11:29                   ` Peter Korsgaard
     [not found]                     ` <87y6d6ie7q.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2010-07-20 11:51                       ` Michael Lawnick [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=4C458DD6.2020306@gmx.de \
    --to=ml.lawnick-mmb7mzphnfy@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@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 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.