| Message ID | 20180812162536.30369-1-hdegoede@redhat.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall | expand |
On Sun, Aug 12, 2018 at 06:25:36PM +0200, Hans de Goede wrote: > GpioInt ACPI event handlers may see there IRQ triggered immediately > after requesting the IRQ (esp. level triggered ones). This means that they > may run before any (builtin) other drivers have had a chance to register > their OpRegion handlers, leading to errors like this: > > [ 1.133274] ACPI Error: No handler for Region [PMOP] ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) > [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no handler (20180531/exfldio-265) > [ 1.133297] ACPI Error: Method parse/execution failed \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) > Hmm, according ACPI 6.2 spec (see chapter 6.5.4 explaining _REG method) the AML code is not supposed to access OpRegions if they are not available (e.g there is no driver loaded). Can you share the AML that triggers the above error?
Hi, On 13-08-18 17:44, Mika Westerberg wrote: > On Sun, Aug 12, 2018 at 06:25:36PM +0200, Hans de Goede wrote: >> GpioInt ACPI event handlers may see there IRQ triggered immediately >> after requesting the IRQ (esp. level triggered ones). This means that they >> may run before any (builtin) other drivers have had a chance to register >> their OpRegion handlers, leading to errors like this: >> >> [ 1.133274] ACPI Error: No handler for Region [PMOP] ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) >> [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no handler (20180531/exfldio-265) >> [ 1.133297] ACPI Error: Method parse/execution failed \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) >> > > Hmm, according ACPI 6.2 spec (see chapter 6.5.4 explaining _REG method) > the AML code is not supposed to access OpRegions if they are not > available (e.g there is no driver loaded). Sure, but there are plenty of cases where AML code does not always does that and even it where to do that, from an interrupt handler like this, that is probably a bad idea, since the handler will clear the interrupt cause, so what ever the code would have done if the OpRegion was in place now will not happen. > Can you share the AML that triggers the above error? Sure but as said there is plenty of AML code around not checking for OpRegions being registered, anyways: https://fedorapeople.org/~jwrdegoede/acpidump.onda-v975w Look for _L01 in the DSDT part, it is the VBUS access there which triggers these errors. Regards, Hans
On Mon, Aug 13, 2018 at 05:53:43PM +0200, Hans de Goede wrote: > Hi, > > On 13-08-18 17:44, Mika Westerberg wrote: > > On Sun, Aug 12, 2018 at 06:25:36PM +0200, Hans de Goede wrote: > > > GpioInt ACPI event handlers may see there IRQ triggered immediately > > > after requesting the IRQ (esp. level triggered ones). This means that they > > > may run before any (builtin) other drivers have had a chance to register > > > their OpRegion handlers, leading to errors like this: > > > > > > [ 1.133274] ACPI Error: No handler for Region [PMOP] ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) > > > [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no handler (20180531/exfldio-265) > > > [ 1.133297] ACPI Error: Method parse/execution failed \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) > > > > > > > Hmm, according ACPI 6.2 spec (see chapter 6.5.4 explaining _REG method) > > the AML code is not supposed to access OpRegions if they are not > > available (e.g there is no driver loaded). > > Sure, but there are plenty of cases where AML code does not always > does that and even it where to do that, from an interrupt handler > like this, that is probably a bad idea, since the handler will > clear the interrupt cause, so what ever the code would have done > if the OpRegion was in place now will not happen. > > > Can you share the AML that triggers the above error? > > Sure but as said there is plenty of AML code around not > checking for OpRegions being registered, anyways: > > https://fedorapeople.org/~jwrdegoede/acpidump.onda-v975w > > Look for _L01 in the DSDT part, it is the VBUS access there > which triggers these errors. :-( I'm pretty sure it fails even in Windows if the interrupt is triggered before the corresponding handler is installed. I guess your solution at least makes it working better with built-in drivers. For modules I think we are still in the same situation but I don't have better ideas right now. Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Hi, On 14-08-18 10:56, Mika Westerberg wrote: > On Mon, Aug 13, 2018 at 05:53:43PM +0200, Hans de Goede wrote: >> Hi, >> >> On 13-08-18 17:44, Mika Westerberg wrote: >>> On Sun, Aug 12, 2018 at 06:25:36PM +0200, Hans de Goede wrote: >>>> GpioInt ACPI event handlers may see there IRQ triggered immediately >>>> after requesting the IRQ (esp. level triggered ones). This means that they >>>> may run before any (builtin) other drivers have had a chance to register >>>> their OpRegion handlers, leading to errors like this: >>>> >>>> [ 1.133274] ACPI Error: No handler for Region [PMOP] ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) >>>> [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no handler (20180531/exfldio-265) >>>> [ 1.133297] ACPI Error: Method parse/execution failed \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) >>>> >>> >>> Hmm, according ACPI 6.2 spec (see chapter 6.5.4 explaining _REG method) >>> the AML code is not supposed to access OpRegions if they are not >>> available (e.g there is no driver loaded). >> >> Sure, but there are plenty of cases where AML code does not always >> does that and even it where to do that, from an interrupt handler >> like this, that is probably a bad idea, since the handler will >> clear the interrupt cause, so what ever the code would have done >> if the OpRegion was in place now will not happen. >> >>> Can you share the AML that triggers the above error? >> >> Sure but as said there is plenty of AML code around not >> checking for OpRegions being registered, anyways: >> >> https://fedorapeople.org/~jwrdegoede/acpidump.onda-v975w >> >> Look for _L01 in the DSDT part, it is the VBUS access there >> which triggers these errors. > > :-( > > I'm pretty sure it fails even in Windows if the interrupt is triggered > before the corresponding handler is installed. I guess your solution at > least makes it working better with built-in drivers. For modules I think > we are still in the same situation but I don't have better ideas right > now. Right, in my experience, as a general rule of thumb, drivers which register OpRegions should simply always be builtin, when they are modules too much stuff breaks. > Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com> Thanks. Regards, Hans
On Sun, 2018-08-12 at 18:25 +0200, Hans de Goede wrote: Thanks for the patch, few comments below. > GpioInt ACPI event handlers may see there IRQ triggered immediately > after requesting the IRQ (esp. level triggered ones). This means that > they > may run before any (builtin) other drivers have had a chance to (builtin) other -> other (builtin) > register > their OpRegion handlers, leading to errors like this: > > [ 1.133274] ACPI Error: No handler for Region [PMOP] > ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) > [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no > handler (20180531/exfldio-265) > [ 1.133297] ACPI Error: Method parse/execution failed > \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) > > We already defer the manual initial trigger of edge triggered > interrupts > by running it from a late_initcall handler, this commit replaces this > with > deferring the entire acpi_gpiochip_request_interrupts() call till > then, > fixing the problem of some OpRegions not being registered yet. > > Note that this removes the need to have a list of edge triggered > handlers > which need to run, since the entire acpi_gpiochip_request_interrupts() > call > is now delayed, acpi_gpiochip_request_interrupt() can call these > directly > now. Should it have Fixes tag? > + struct list_head deferred_req_irqs_list_entry; Can we drop 'req' part from the name? It's way too long already. I think we have enough context to understand to which list it will be chained to. > +static DEFINE_MUTEX(acpi_gpio_deferred_req_irqs_lock); > +static LIST_HEAD(acpi_gpio_deferred_req_irqs_list); > +static bool acpi_gpio_deferred_req_irqs_done; Ditto. > + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); > + defer = !acpi_gpio_deferred_req_irqs_done; > + if (defer) > + list_add(&acpi_gpio->deferred_req_irqs_list_entry, > + &acpi_gpio_deferred_req_irqs_list); > + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); > + > + if (defer) > + return; You might need no temporary variable if you rearrange the above like lock() if (...) { list_add(); unlock(); return; } unlock(); (Personally I like this slightly more, but have not been insisting.) > + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); > + if (!list_empty(&acpi_gpio->deferred_req_irqs_list_entry)) > + list_del_init(&acpi_gpio->deferred_req_irqs_list_entry); Side note. This trick I start seeing more often, perhaps in the future something like generic macro will be available. > + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); > +/* Run deferred acpi_gpiochip_request_interrupts() */ > +static int acpi_gpio_handle_deferred_request_interrupts(void) > { > + struct acpi_gpio_chip *acpi_gpio, *tmp; > + > + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); > + list_for_each_entry_safe(acpi_gpio, tmp, > + &acpi_gpio_deferred_req_irqs_list, > + deferred_req_irqs_list_entry) { > + acpi_handle handle; > + handle = ACPI_HANDLE(acpi_gpio->chip->parent); > + if (handle) Since you are not checking return code the below is NULL aware for handle parameter. > + acpi_walk_resources(handle, "_AEI", > + acpi_gpiochip_request_interr > upt, > + acpi_gpio); > + > + list_del_init(&acpi_gpio->deferred_req_irqs_list_entry); > }
Hi, On 14-08-18 13:02, Andy Shevchenko wrote: > On Sun, 2018-08-12 at 18:25 +0200, Hans de Goede wrote: > > Thanks for the patch, few comments below. > >> GpioInt ACPI event handlers may see there IRQ triggered immediately >> after requesting the IRQ (esp. level triggered ones). This means that >> they >> may run before any (builtin) other drivers have had a chance to > > (builtin) other -> other (builtin) Fixed for v2. >> register >> their OpRegion handlers, leading to errors like this: >> >> [ 1.133274] ACPI Error: No handler for Region [PMOP] >> ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) >> [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no >> handler (20180531/exfldio-265) >> [ 1.133297] ACPI Error: Method parse/execution failed >> \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) >> >> We already defer the manual initial trigger of edge triggered >> interrupts >> by running it from a late_initcall handler, this commit replaces this >> with >> deferring the entire acpi_gpiochip_request_interrupts() call till >> then, >> fixing the problem of some OpRegions not being registered yet. >> >> Note that this removes the need to have a list of edge triggered >> handlers >> which need to run, since the entire acpi_gpiochip_request_interrupts() >> call >> is now delayed, acpi_gpiochip_request_interrupt() can call these >> directly >> now. > > Should it have Fixes tag? I cannot come up with a specific commit this fixes, this is more of a generic pre-existing issue then anything introduced by a specific commit, so no. > >> + struct list_head deferred_req_irqs_list_entry; > > Can we drop 'req' part from the name? It's way too long already. I think > we have enough context to understand to which list it will be chained > to. We are not deferring the IRQ, we are deferring the _requesting_ of the IRQ, and this fits in 80 chars in most places fine, and there where it does not dropping the _req is not going to help, so I would prefer to keep this as is. >> +static DEFINE_MUTEX(acpi_gpio_deferred_req_irqs_lock); >> +static LIST_HEAD(acpi_gpio_deferred_req_irqs_list); >> +static bool acpi_gpio_deferred_req_irqs_done; > > Ditto. > >> + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); >> + defer = !acpi_gpio_deferred_req_irqs_done; >> + if (defer) >> + list_add(&acpi_gpio->deferred_req_irqs_list_entry, >> + &acpi_gpio_deferred_req_irqs_list); >> + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); >> + >> + if (defer) >> + return; > > You might need no temporary variable if you rearrange the above like > > lock() > if (...) { > list_add(); > unlock(); > return; > } > unlock(); > > (Personally I like this slightly more, but have not been insisting.) Sorry, but no / nack, I really dislike constructions where lock and unlock are not balanced 1:1. I personally really dislike unlock before return code like you suggest and always suggest people to use a goto to the actual normal exit path unlock, setting retval before the goto. > >> + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); > >> + if (!list_empty(&acpi_gpio->deferred_req_irqs_list_entry)) >> + list_del_init(&acpi_gpio->deferred_req_irqs_list_entry); > > Side note. This trick I start seeing more often, perhaps in the future > something like generic macro will be available. > >> + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); > >> +/* Run deferred acpi_gpiochip_request_interrupts() */ >> +static int acpi_gpio_handle_deferred_request_interrupts(void) >> { >> + struct acpi_gpio_chip *acpi_gpio, *tmp; >> + >> + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); >> + list_for_each_entry_safe(acpi_gpio, tmp, >> + &acpi_gpio_deferred_req_irqs_list, >> + deferred_req_irqs_list_entry) { >> + acpi_handle handle; > >> + handle = ACPI_HANDLE(acpi_gpio->chip->parent); > >> + if (handle) > > Since you are not checking return code the below is NULL aware for > handle parameter. Ah, ok I will drop the check for v2. >> + acpi_walk_resources(handle, "_AEI", >> + acpi_gpiochip_request_interr >> upt, >> + acpi_gpio); >> + >> + list_del_init(&acpi_gpio->deferred_req_irqs_list_entry); >> } > > Regards, Hans
diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c index addd9fecc198..a4139a187151 100644 --- a/drivers/gpio/gpiolib-acpi.c +++ b/drivers/gpio/gpiolib-acpi.c @@ -25,7 +25,6 @@ struct acpi_gpio_event { struct list_head node; - struct list_head initial_sync_list; acpi_handle handle; unsigned int pin; unsigned int irq; @@ -49,10 +48,19 @@ struct acpi_gpio_chip { struct mutex conn_lock; struct gpio_chip *chip; struct list_head events; + struct list_head deferred_req_irqs_list_entry; }; -static LIST_HEAD(acpi_gpio_initial_sync_list); -static DEFINE_MUTEX(acpi_gpio_initial_sync_list_lock); +/* + * For gpiochips which call acpi_gpiochip_request_interrupts() before late_init + * (so builtin drivers) we register the ACPI GpioInt event handlers from a + * late_initcall_sync handler, so that other builtin drivers can register their + * OpRegions before the event handlers can run. This list contains gpiochips + * for which the acpi_gpiochip_request_interrupts() has been deferred. + */ +static DEFINE_MUTEX(acpi_gpio_deferred_req_irqs_lock); +static LIST_HEAD(acpi_gpio_deferred_req_irqs_list); +static bool acpi_gpio_deferred_req_irqs_done; static int acpi_gpiochip_find(struct gpio_chip *gc, void *data) { @@ -89,21 +97,6 @@ static struct gpio_desc *acpi_get_gpiod(char *path, int pin) return gpiochip_get_desc(chip, pin); } -static void acpi_gpio_add_to_initial_sync_list(struct acpi_gpio_event *event) -{ - mutex_lock(&acpi_gpio_initial_sync_list_lock); - list_add(&event->initial_sync_list, &acpi_gpio_initial_sync_list); - mutex_unlock(&acpi_gpio_initial_sync_list_lock); -} - -static void acpi_gpio_del_from_initial_sync_list(struct acpi_gpio_event *event) -{ - mutex_lock(&acpi_gpio_initial_sync_list_lock); - if (!list_empty(&event->initial_sync_list)) - list_del_init(&event->initial_sync_list); - mutex_unlock(&acpi_gpio_initial_sync_list_lock); -} - static irqreturn_t acpi_gpio_irq_handler(int irq, void *data) { struct acpi_gpio_event *event = data; @@ -229,7 +222,6 @@ static acpi_status acpi_gpiochip_request_interrupt(struct acpi_resource *ares, event->irq = irq; event->pin = pin; event->desc = desc; - INIT_LIST_HEAD(&event->initial_sync_list); ret = request_threaded_irq(event->irq, NULL, handler, irqflags, "ACPI:Event", event); @@ -251,10 +243,9 @@ static acpi_status acpi_gpiochip_request_interrupt(struct acpi_resource *ares, * may refer to OperationRegions from other (builtin) drivers which * may be probed after us. */ - if (handler == acpi_gpio_irq_handler && - (((irqflags & IRQF_TRIGGER_RISING) && value == 1) || - ((irqflags & IRQF_TRIGGER_FALLING) && value == 0))) - acpi_gpio_add_to_initial_sync_list(event); + if (((irqflags & IRQF_TRIGGER_RISING) && value == 1) || + ((irqflags & IRQF_TRIGGER_FALLING) && value == 0)) + handler(event->irq, event); return AE_OK; @@ -283,6 +274,7 @@ void acpi_gpiochip_request_interrupts(struct gpio_chip *chip) struct acpi_gpio_chip *acpi_gpio; acpi_handle handle; acpi_status status; + bool defer; if (!chip->parent || !chip->to_irq) return; @@ -295,6 +287,16 @@ void acpi_gpiochip_request_interrupts(struct gpio_chip *chip) if (ACPI_FAILURE(status)) return; + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); + defer = !acpi_gpio_deferred_req_irqs_done; + if (defer) + list_add(&acpi_gpio->deferred_req_irqs_list_entry, + &acpi_gpio_deferred_req_irqs_list); + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); + + if (defer) + return; + acpi_walk_resources(handle, "_AEI", acpi_gpiochip_request_interrupt, acpi_gpio); } @@ -325,11 +327,14 @@ void acpi_gpiochip_free_interrupts(struct gpio_chip *chip) if (ACPI_FAILURE(status)) return; + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); + if (!list_empty(&acpi_gpio->deferred_req_irqs_list_entry)) + list_del_init(&acpi_gpio->deferred_req_irqs_list_entry); + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); + list_for_each_entry_safe_reverse(event, ep, &acpi_gpio->events, node) { struct gpio_desc *desc; - acpi_gpio_del_from_initial_sync_list(event); - if (irqd_is_wakeup_set(irq_get_irq_data(event->irq))) disable_irq_wake(event->irq); @@ -1049,6 +1054,7 @@ void acpi_gpiochip_add(struct gpio_chip *chip) acpi_gpio->chip = chip; INIT_LIST_HEAD(&acpi_gpio->events); + INIT_LIST_HEAD(&acpi_gpio->deferred_req_irqs_list_entry); status = acpi_attach_data(handle, acpi_gpio_chip_dh, acpi_gpio); if (ACPI_FAILURE(status)) { @@ -1195,20 +1201,30 @@ bool acpi_can_fallback_to_crs(struct acpi_device *adev, const char *con_id) return con_id == NULL; } -/* Sync the initial state of handlers after all builtin drivers have probed */ -static int acpi_gpio_initial_sync(void) +/* Run deferred acpi_gpiochip_request_interrupts() */ +static int acpi_gpio_handle_deferred_request_interrupts(void) { - struct acpi_gpio_event *event, *ep; + struct acpi_gpio_chip *acpi_gpio, *tmp; + + mutex_lock(&acpi_gpio_deferred_req_irqs_lock); + list_for_each_entry_safe(acpi_gpio, tmp, + &acpi_gpio_deferred_req_irqs_list, + deferred_req_irqs_list_entry) { + acpi_handle handle; - mutex_lock(&acpi_gpio_initial_sync_list_lock); - list_for_each_entry_safe(event, ep, &acpi_gpio_initial_sync_list, - initial_sync_list) { - acpi_evaluate_object(event->handle, NULL, NULL, NULL); - list_del_init(&event->initial_sync_list); + handle = ACPI_HANDLE(acpi_gpio->chip->parent); + if (handle) + acpi_walk_resources(handle, "_AEI", + acpi_gpiochip_request_interrupt, + acpi_gpio); + + list_del_init(&acpi_gpio->deferred_req_irqs_list_entry); } - mutex_unlock(&acpi_gpio_initial_sync_list_lock); + + acpi_gpio_deferred_req_irqs_done = true; + mutex_unlock(&acpi_gpio_deferred_req_irqs_lock); return 0; } /* We must use _sync so that this runs after the first deferred_probe run */ -late_initcall_sync(acpi_gpio_initial_sync); +late_initcall_sync(acpi_gpio_handle_deferred_request_interrupts);
GpioInt ACPI event handlers may see there IRQ triggered immediately after requesting the IRQ (esp. level triggered ones). This means that they may run before any (builtin) other drivers have had a chance to register their OpRegion handlers, leading to errors like this: [ 1.133274] ACPI Error: No handler for Region [PMOP] ((____ptrval____)) [UserDefinedRegion] (20180531/evregion-132) [ 1.133286] ACPI Error: Region UserDefinedRegion (ID=141) has no handler (20180531/exfldio-265) [ 1.133297] ACPI Error: Method parse/execution failed \_SB.GPO2._L01, AE_NOT_EXIST (20180531/psparse-516) We already defer the manual initial trigger of edge triggered interrupts by running it from a late_initcall handler, this commit replaces this with deferring the entire acpi_gpiochip_request_interrupts() call till then, fixing the problem of some OpRegions not being registered yet. Note that this removes the need to have a list of edge triggered handlers which need to run, since the entire acpi_gpiochip_request_interrupts() call is now delayed, acpi_gpiochip_request_interrupt() can call these directly now. Signed-off-by: Hans de Goede <hdegoede@redhat.com> --- drivers/gpio/gpiolib-acpi.c | 86 ++++++++++++++++++++++--------------- 1 file changed, 51 insertions(+), 35 deletions(-)