From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Peter Korsgaard
<peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@public.gmane.org>
Cc: ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ml.lawnick-Mmb7MZpHnFY@public.gmane.org
Subject: Re: [PATCHv4] i2c: add generic I2C multiplexer using gpio api
Date: Tue, 30 Nov 2010 17:15:39 +0100 [thread overview]
Message-ID: <20101130171539.73e8e799@endymion.delvare> (raw)
In-Reply-To: <1291125788-9433-1-git-send-email-peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@public.gmane.org>
Hi Peter,
On Tue, 30 Nov 2010 15:03:08 +0100, Peter Korsgaard wrote:
> Add an i2c mux driver providing access to i2c bus segments using a
> hardware MUX sitting on a master bus and controlled through gpio pins.
>
> E.G. something like:
>
> ---------- ---------- Bus segment 1 - - - - -
> | | SCL/SDA | |-------------- | |
> | |------------| |
> | | | | Bus segment 2 | |
> | Linux | GPIO 1..N | MUX |--------------- Devices
> | |------------| | | |
> | | | | Bus segment M
> | | | |---------------| |
> ---------- ---------- - - - - -
>
> SCL/SDA of the master I2C bus is multiplexed to bus segment 1..M
> according to the settings of the GPIO pins 1..N.
I've fixed two remaining minor things myself, and your patch is ready
to be applied now, except for one issue I just noticed. See below.
> (..)
> --- /dev/null
> +++ b/Documentation/i2c/muxes/gpio-i2cmux
> (...)
> +Usage
> +-----
> +
> +gpio-i2cmux uses the platform bus, so you need to provide a struct
> +platform_device with the platform_data pointing to a struct
> +gpio_i2cmux_platform_data with the I2C adapter number of the master
> +bus, the number bus segments to create and the GPIO pins used
"of" got lost in the battle, I've added it back.
> +to control it. See include/linux/gpio-i2cmux.h for details.
> (...)
> --- /dev/null
> +++ b/drivers/i2c/muxes/gpio-i2cmux.c
> (...)
> + for (i = 0; i < pdata->n_gpios; i++) {
> + ret = gpio_request(pdata->gpios[i], "gpio-i2cmux");
> + if (ret)
> + goto err_request_gpio;
> + gpio_direction_output(pdata->gpios[i], pdata->idle & (1 << i));
This looks wrong if pdata->idle == GPIO_I2CMUX_NO_IDLE. I think we want
something along the lines of:
unsigned initial_state;
initial_state = pdata->idle == GPIO_I2CMUX_NO_IDLE ?
pdata->values[0] : pdata->idle;
(...)
gpio_direction_output(pdata->gpios[i], initial_state & (1 << i));
What do you think? An alternative is to leave the direction
uninitialized and hope it's already OK, but I'm not sure how realistic
this is.
> + }
> +
> +
Double blank line, I've removed one.
> + if (pdata->idle != GPIO_I2CMUX_NO_IDLE)
> + deselect = gpiomux_deselect;
--
Jean Delvare
next prev parent reply other threads:[~2010-11-30 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 14:03 [PATCHv4] i2c: add generic I2C multiplexer using gpio api Peter Korsgaard
[not found] ` <1291125788-9433-1-git-send-email-peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@public.gmane.org>
2010-11-30 16:15 ` Jean Delvare [this message]
[not found] ` <20101130171539.73e8e799-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-11-30 19:44 ` Peter Korsgaard
[not found] ` <871v62y4ts.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2010-11-30 20:03 ` 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=20101130171539.73e8e799@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@public.gmane.org \
--cc=peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@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).