Hi Michael,
On Mon, 18 Oct 2010 10:55:57 +0100, Hennerich, Michael wrote:
> Jean Delvare wrote on 2010-10-18:
> > Hi Mike,
> >
> > On Sun, 17 Oct 2010 19:43:39 -0400, Mike Frysinger wrote:
> >> From: Michael Hennerich <michael.hennerich@xxxxxxxxxx>
> >>
> >> These flags can be optionally defined - slave drivers may use them as
> >> flags argument for request_irq(). In case they are left uninitialized
> >> they will default to zero, and therefore shouldn't cause problems.
> >>
> >> This allows us to avoid having to add dedicated platform init code
> >> just to call set_irq_type()
> >
> > Do you have examples of this? Can we see a preview of the amount of
> > cleanups this patch would allow?
>
> Examples can be found in various board setup files:
>
> One example arch/sh/boards/mach-ecovec24/setup.c:
>
> static struct i2c_board_info ts_i2c_clients = {
> I2C_BOARD_INFO("tsc2007", 0x48),
> .type = "tsc2007",
> .platform_data = &tsc2007_info,
> .irq = IRQ0,
> };
>
> [--snip--]
>
> /* enable TouchScreen */
> i2c_register_board_info(0, &ts_i2c_clients, 1);
> set_irq_type(IRQ0, IRQ_TYPE_LEVEL_LOW);
This example doesn't quite match the patch description. There's no
"dedicated platform init code just to call set_irq_type()", as you
already have platform code to call i2c_register_board_info(). It's
really only calling set_irq_type() from platform code vs. from driver
code.
> >> -- which doesn't work very well when coupled with module drivers.
> >
> > I don't quite get what you mean here.
>
> Since the driver doesn't setup the irq_type itself you need to do it
> manually in advance using set_irq_type().
> This happens most likely from your paltform setup/configuration file.
>
> Assuming the driver is built as a module, this code gets executed unconditionally,
> no matter if the driver gets finally loaded or not.
>
> Assuming you have several drivers build as modules, using the same irq but with
> different irq types, you run into problems here.
I do not get why.
You're not going to register several I2C devices using the same IRQ but
requiring different IRQ flags anyway, as it wouldn't work. So you'll
have to only register the I2C devices which are actually present on the
system. Setting the IRQ type at the same time or deferring this action
to the driver(s) doesn't make any difference then, does it?
> There are some development boards featuring extension options, which all plug on the same
> socket but required different drivers/irq types.
How do you figure out which extension option is plugged? You can't
instantiate an I2C device which isn't present, so you must have a way
to know what extension option is used, to instantiate the right I2C
device at the right address.
> The ideal way is therefore to pass the irq_flags together with the SPI/I2C board info.
All I see so far is two data structures made slightly larger, for no
actual benefit.
--
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
