From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Lawnick Subject: Re: [PATCH] i2c: add generic I2C multiplexer using gpio api Date: Tue, 20 Jul 2010 13:09:39 +0200 Message-ID: <4C4583F3.8080807@gmx.de> References: <1278285584-13632-1-git-send-email-peter.korsgaard@barco.com> <87fwzejz1v.fsf@macbook.be.48ers.dk> <20100720115005.3b3fa865@hyperion.delvare> <87bpa2jwzy.fsf@macbook.be.48ers.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87bpa2jwzy.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Peter Korsgaard Cc: Jean Delvare , ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org, linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org Peter Korsgaard said the following: >>>>>> "Jean" == Jean Delvare writes: > > Hi, > > Jean> Michael and myself are in the process of adding core support for > Jean> bus multiplexing to the i2c subsystem. There is no point in > Jean> reviewing more specific implementations until the core part is > Jean> merged (which is scheduled to happen in kernel 2.6.36.) > > But this patch is independent from that work as the mux access isn't > through I2C, hence no changes to i2c-core needed. i2c-mux patch does not expect path control via i2c. Your scenario fits perfectly. -- KR Michael Lawnick