gpio: pca953x: Synchronize interrupt handler properly
PATCH 1/4 gpio: pca953x: Synchronize interrupt handler properly
Since the commit aa58a21ae378 ("gpio: pca953x: disable regmap locking") the locking of regmap is disabled and that immediately introduces a synchronization issue. It's easy to see when we try to monitor more than one interrupt from the same chip.
It seems that the problem exists from the day one and even commit 6e20fb18054c ("drivers/gpio/pca953x.c: add a mutex to fix race condition") missed this.
Below are the traces and shell reproducers before and after proposed change. Note duplicates in the IRQ events. /proc/interrupts also shows a deviation, i.e. sum of children interrupts higher than parent's one.
When locking is disabled for regmap and no protection in IRQ handler
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...
gpioset-194 regmap_hw_write_start: i2c-INT3491:02 reg=2 count=1 irq/31-i2c-INT3-139 regmap_hw_read_start: i2c-INT3491:02 reg=4c count=2 gpioset-194 regmap_hw_write_done: i2c-INT3491:02 reg=2 count=1 gpioset-194 regmap_reg_read_cache: i2c-INT3491:02 reg=6 val=f5 gpioset-194 regmap_reg_write: i2c-INT3491:02 reg=6 val=f5 gpioset-194 regmap_hw_write_start: i2c-INT3491:02 reg=6 count=1 irq/31-i2c-INT3-139 regmap_hw_read_done: i2c-INT3491:02 reg=4c count=2
...
% gpiomon gpiochip3 0 &
% gpioset gpiochip3 1=0
% gpioset gpiochip3 1=1
event: RISING EDGE offset: 0 timestamp: [ 302.782583765]
% gpiomon gpiochip3 2 &
% gpioset gpiochip3 1=0
event: RISING EDGE offset: 2 timestamp: [ 312.033148829]
event: FALLING EDGE offset: 0 timestamp: [ 312.022757525]
% gpioset gpiochip3 1=1
event: RISING EDGE offset: 2 timestamp: [ 316.201148473] event: RISING EDGE offset: 0 timestamp: [ 316.191759599]
When locking is disabled for regmap and protection in IRQ handler
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...
gpioset-202 regmap_hw_write_start: i2c-INT3491:02 reg=2 count=1 gpioset-202 regmap_hw_write_done: i2c-INT3491:02 reg=2 count=1 gpioset-202 regmap_reg_read_cache: i2c-INT3491:02 reg=6 val=fd gpioset-202 regmap_reg_write: i2c-INT3491:02 reg=6 val=fd gpioset-202 regmap_hw_write_start: i2c-INT3491:02 reg=6 count=1 gpioset-202 regmap_hw_write_done: i2c-INT3491:02 reg=6 count=1 irq/31-i2c-INT3-139 regmap_hw_read_start: i2c-INT3491:02 reg=4c count=2 irq/31-i2c-INT3-139 regmap_hw_read_done: i2c-INT3491:02 reg=4c count=2
...
% gpiomon gpiochip3 0 &
% gpioset gpiochip3 1=0
event: FALLING EDGE offset: 0 timestamp: [ 531.330078107]
% gpioset gpiochip3 1=1
event: RISING EDGE offset: 0 timestamp: [ 532.912239128]
% gpiomon gpiochip3 2 &
% gpioset gpiochip3 1=0
event: FALLING EDGE offset: 0 timestamp: [ 539.633669484]
% gpioset gpiochip3 1=1
event: RISING EDGE offset: 0 timestamp: [ 542.256978461]
Depends-on: 35d13d94893f ("gpio: pca953x: convert to use bitmap API")
Depends-on: 49427232764d ("gpio: pca953x: Perform basic regmap conversion")
--- drivers/gpio/gpio-pca953x.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/gpio/gpio-pca953x.c +5 -3
@@ -734,14 +734,16 @@ static irqreturn_t pca953x_irq_handler(int irq, void *devid)struct gpio_chip *gc = &chip->gpio_chip;DECLARE_BITMAP (pending,MAX_LINE );int level; +bool ret; -if (!pca953x_irq_pending (chip, pending)) -return IRQ_NONE ; +mutex_lock (&chip->i2c_lock); + ret =pca953x_irq_pending (chip, pending); +mutex_unlock (&chip->i2c_lock);for_each_set_bit (level, pending, gc->ngpio)handle_nested_irq (irq_find_mapping (gc->irq.domain, level)); -return IRQ_HANDLED ; +return IRQ_RETVAL (ret); }static int pca953x_irq_setup (struct pca953x_chip *chip,int irq_base)
Signature · 1 line
2.27.0.rc2
PATCH 2/4 gpio: pca953x: Override IRQ for one of the expanders on Galileo Gen 2
ACPI table on Intel Galileo Gen 2 has wrong pin number for IRQ resource of one of the I²C GPIO expanders. Since we know what that number is and luckily have GPIO bases fixed for SoC's controllers, we may use a simple DMI quirk to match the platform and retrieve GpioInt() pin on it for the expander in question.
Mika suggested the way to avoid a quirk in the GPIO ACPI library and here is the second, almost rewritten version of it.
Depends-on: 25e3ef894eef ("gpio: acpi: Split out acpi_gpio_get_irq_resource() helper")
--- drivers/gpio/gpio-pca953x.c | 79 +++++++++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+)
drivers/gpio/gpio-pca953x.c +79 -0
@@ -107,6 +107,79 @@ static const struct i2c_device_id pca953x_id[] = { };MODULE_DEVICE_TABLE (i2c, pca953x_id); +#ifdef CONFIG_GPIO_PCA953X_IRQ + +#include <linux/dmi.h> +#include <linux/gpio.h> +#include <linux/list.h> + +static const struct dmi_system_id pca953x_dmi_acpi_irq_info[] = { + { +/* +* On Intel Galileo Gen 2 board the IRQ pin of one of +* the I²C GPIO expanders, which has GpioInt() resource, +* is provided as an absolute number instead of being +* relative. Since first controller (gpio-sch.c) and +* second (gpio-dwapb.c) are at the fixed bases, we may +* safely refer to the number in the global space to get +* an IRQ out of it. +*/ + .matches = { +DMI_EXACT_MATCH (DMI_BOARD_NAME ,"GalileoGen2" ), + }, + }, + {} +}; + +#ifdef CONFIG_ACPI +static int pca953x_acpi_get_pin (struct acpi_resource *ares,void *data) +{ +struct acpi_resource_gpio *agpio; +int *pin = data; + +if (acpi_gpio_get_irq_resource (ares, &agpio)) + *pin = agpio->pin_table[0 ]; +return 1 ; +} + +static int pca953x_acpi_find_pin (struct device *dev) +{ +struct acpi_device *adev =ACPI_COMPANION (dev); +int pin = -ENOENT , ret; +LIST_HEAD (r); + + ret =acpi_dev_get_resources (adev, &r, pca953x_acpi_get_pin, &pin); +acpi_dev_free_resource_list (&r); +if (ret <0 ) +return ret; + +return pin; +} +#else +static inline int pca953x_acpi_find_pin (struct device *dev) {return -ENXIO ; } +#endif + +static int pca953x_acpi_get_irq (struct device *dev) +{ +int pin, ret; + + pin =pca953x_acpi_find_pin (dev); +if (pin <0 ) +return pin; + +dev_info (dev,"Applying ACPI interrupt quirk (GPIO %d)\n" , pin); + +if (!gpio_is_valid (pin)) +return -EINVAL ; + + ret =gpio_request (pin,"pca953x interrupt" ); +if (ret) +return ret; + +return gpio_to_irq (pin); +} +#endif +static const struct acpi_device_id pca953x_acpi_ids[] = { {"INT3491" ,16 |PCA953X_TYPE |PCA_LATCH_INT , }, { }
@@ -754,6 +827,12 @@ static int pca953x_irq_setup(struct pca953x_chip *chip, int irq_base)DECLARE_BITMAP (irq_stat,MAX_LINE );int ret; +if (dmi_first_match (pca953x_dmi_acpi_irq_info)) { + ret =pca953x_acpi_get_irq (&client->dev); +if (ret >0 ) + client->irq = ret; + } +if (!client->irq)return 0 ;
Signature · 1 line
2.27.0.rc2
PATCH 3/4 gpio: pca953x: Fix direction setting when configure an IRQ
In reply to Andy ShevchenkoThe commit 0f25fda840a9 ("gpio: pca953x: Zap ad-hoc reg_direction cache") seems inadvertently made a typo in pca953x_irq_bus_sync_unlock().
When the direction bit is 1 it means input, and the piece of code in question was looking for output ones that should be turned to inputs.
Fix direction setting when configure an IRQ by injecting a bitmap complement operation.
Depends-on: 35d13d94893f ("gpio: pca953x: convert to use bitmap API")
--- drivers/gpio/gpio-pca953x.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/gpio/gpio-pca953x.c +4 -2
@@ -696,8 +696,6 @@ static void pca953x_irq_bus_sync_unlock(struct irq_data *d)DECLARE_BITMAP (reg_direction,MAX_LINE );int level; -pca953x_read_regs (chip, chip->regs->direction, reg_direction); -if (chip->driver_data &PCA_PCAL ) {/* Enable latch on interrupt-enabled inputs */ pca953x_write_regs (chip,PCAL953X_IN_LATCH , chip->irq_mask);
@@ -708,7 +706,11 @@ static void pca953x_irq_bus_sync_unlock(struct irq_data *d)pca953x_write_regs (chip,PCAL953X_INT_MASK , irq_mask); } +/* Switch direction to input if needed */ +pca953x_read_regs (chip, chip->regs->direction, reg_direction); +bitmap_or (irq_mask, chip->irq_trig_fall, chip->irq_trig_raise, gc->ngpio); +bitmap_complement (reg_direction, reg_direction, gc->ngpio);bitmap_and (irq_mask, irq_mask, reg_direction, gc->ngpio);/* Look for any newly setup interrupt */
Signature · 1 line
2.27.0.rc2
PATCH 4/4 gpio: pca953x: disable regmap locking for automatic address incrementing
In reply to Andy ShevchenkoIt's a repetition of the commit aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:
This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
--- drivers/gpio/gpio-pca953x.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpio/gpio-pca953x.c +1 -0
@@ -395,6 +395,7 @@ static const struct regmap_config pca953x_ai_i2c_regmap = { .writeable_reg = pca953x_writeable_register, .volatile_reg = pca953x_volatile_register, + .disable_locking = true, .cache_type = REGCACHE_RBTREE, .max_register = 0x7f, };
Signature · 1 line
2.27.0.rc2
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Quoted 11 lines · Andy Shevchenko
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>
Ah, good catch. I assume that I didn't have aa58a21ae378 in my tree when I created the patch that then became bcf41dc480b1.
Looks right
Thanks
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Quoted 13 lines · Uwe Kleine-König
Quoted 11 lines · Andy Shevchenko
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>
Quoted 6 lines
Ah, good catch. I assume that I didn't have
aa58a21ae378in my tree when I created the patch that then becamebcf41dc480b1.Looks right
Reviewed-by Uwe Kleine-König <[email protected]>
Thanks!
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Hello,
[adding Geert to Cc as he was involved withaa58a21ae37894d456a2f91a37e9fd71ad4aa27e]
Quoted 17 lines · Andy Shevchenko
Quoted 16 lines · Uwe Kleine-König
Quoted 11 lines · Andy Shevchenko
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>Ah, good catch. I assume that I didn't have
aa58a21ae378in my tree when I created the patch that then becamebcf41dc480b1.
Quoted 8 lines
Quoted 3 lines
Looks right
Reviewed-by Uwe Kleine-König <[email protected]>Thanks!
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
I didn't test but I wonder if this patch is really urgent. Just from looking I'd say two locks are not nice but also don't hurt much. If it is more urgent the commit log should maybe mention how the driver is broken without this change? (Also applies to aa58a21ae37894d456a2f91a37e9fd71ad4aa27e of course (but too late).)
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Quoted 26 lines · Uwe Kleine-König
Hello,
[adding Geert to Cc as he was involved with
aa58a21ae37894d456a2f91a37e9fd71ad4aa27e]Quoted 19 lines · Andy Shevchenko
Quoted 18 lines · Uwe Kleine-König
Quoted 11 lines · Andy Shevchenko
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>Ah, good catch. I assume that I didn't have
aa58a21ae378in my tree when I created the patch that then becamebcf41dc480b1.Looks right
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
Reviewed-by Uwe Kleine-König <[email protected]>Thanks!
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
I didn't test but I wonder if this patch is really urgent.
I'm talking about this entire fix-series.
Quoted 5 lines
Just from
looking I'd say two locks are not nice but also don't hurt much. If it is more urgent the commit log should maybe mention how the driver is broken without this change? (Also applies toaa58a21ae37894d456a2f91a37e9fd71ad4aa27eof course (but too late).)
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Quoted 30 lines · Andy Shevchenko
Quoted 28 lines · Uwe Kleine-König
Hello,
[adding Geert to Cc as he was involved with
aa58a21ae37894d456a2f91a37e9fd71ad4aa27e]Quoted 21 lines · Andy Shevchenko
Quoted 19 lines · Uwe Kleine-König
Quoted 11 lines · Andy Shevchenko
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>Ah, good catch. I assume that I didn't have
aa58a21ae378in my tree when I created the patch that then becamebcf41dc480b1.Looks right
Reviewed-by Uwe Kleine-König <[email protected]>
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Thanks!
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
I didn't test but I wonder if this patch is really urgent.
I'm talking about this entire fix-series.
Ah, I didn't notice this is a series as I only got patch 4.
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Quoted 27 lines · Uwe Kleine-König
Quoted 26 lines · Andy Shevchenko
Quoted 24 lines · Uwe Kleine-König
Quoted 23 lines · Andy Shevchenko
Quoted 13 lines · Uwe Kleine-König
Quoted 11 lines · Andy Shevchenko
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>Quoted 6 lines
Ah, good catch. I assume that I didn't have
aa58a21ae378in my tree when I created the patch that then becamebcf41dc480b1.Looks right
Reviewed-by Uwe Kleine-König <[email protected]>Thanks!
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
I didn't test but I wonder if this patch is really urgent.
I'm talking about this entire fix-series.
Ah, I didn't notice this is a series as I only got patch 4.
In case you are curious / want to try:
https://lore.kernel.org/linux-gpio/[email protected]/T/#m5e01e6462f2f72fbc4bdd3f71c330b7a2f75d5ba
Signature · 2 lines
With Best Regards, Andy Shevchenko
Bartosz Golaszewski
AppliedRe: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
In reply to Andy Shevchenkopon., 15 cze 2020 o 14:53 Andy Shevchenko
<[email protected]> napisał(a):
Quoted 22 lines · Uwe Kleine-König
Quoted 13 lines · Andy Shevchenko
Quoted 11 lines
It's a repetition of the commit
aa58a21ae378
("gpio: pca953x: disable regmap locking")
which states the following:This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing")Cc Uwe Kleine-König <[email protected]>Signed-off-by Andy Shevchenko <[email protected]>Quoted 6 lines
Ah, good catch. I assume that I didn't have
aa58a21ae378in my tree when I created the patch that then becamebcf41dc480b1.Looks right
Reviewed-by Uwe Kleine-König <[email protected]>
Quoted 10 lines
Thanks!
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
--
With Best Regards,
Andy Shevchenko
I applied the whole series for fixes. Thanks!
Bartosz
Re: [PATCH v1 4/4] gpio: pca953x: disable regmap locking for automatic address incrementing
Quoted 4 lines · Bartosz Golaszewski
pon., 15 cze 2020 o 14:53 Andy Shevchenko
<[email protected]> napisał(a):Quoted 2 lines · Uwe Kleine-König
Quoted 1 line · Andy Shevchenko
...
Quoted 10 lines
Quoted 8 lines
Quoted 3 lines
Looks right
Reviewed-by Uwe Kleine-König <[email protected]>Thanks!
Linus, Bart, just to clarify that this is material for one of the next v5.8-rcX (this cycle!).
I applied the whole series for fixes. Thanks!
Thank you!
Signature · 2 lines
With Best Regards, Andy Shevchenko