What's the frequency of the letter "o" in:
Feb. 7, 2019, 6:59 p.m.
egranata@google.com - Feb. 7, 2019, 6:59 p.m.
information about interrupts mediated via a GPIO controller.
directly to the driver as an IRQ number.
does not try to parse GpioInt() resources.
This commit adds that functionality.
Rafael J. Wysocki - Feb. 7, 2019, 7:02 p.m.
> information about interrupts mediated via a GPIO controller.
> directly to the driver as an IRQ number.
> does not try to parse GpioInt() resources.
> This commit adds that functionality.
> +        * as a last resort.
Andy Shevchenko - Feb. 7, 2019, 7:39 p.m.
> > information about interrupts mediated via a GPIO controller.
> > directly to the driver as an IRQ number.
> > does not try to parse GpioInt() resources.
> > This commit adds that functionality.
needs to register an interrupt out of GpioIo() resource?
Andy Shevchenko - Feb. 7, 2019, 7:45 p.m.
> > > This commit adds that functionality.
> needs to register an interrupt out of GpioIo() resource?
How to always get second resource?
egranata@google.com - Feb. 7, 2019, 7:55 p.m.
Resending as plain text; comments inlined.
> > > information about interrupts mediated via a GPIO controller.
> > > directly to the driver as an IRQ number.
> > > does not try to parse GpioInt() resources.
> And why is this a problem?
Do you have any suggestions to write proper firmware tables to avoid this issue?
Andy Shevchenko - Feb. 7, 2019, 8:18 p.m.
>> > > does not try to parse GpioInt() resources.
>> And why is this a problem?
> look for GpioInt resources, it seemed to us to make more sense to extend platform_get_irq() instead.
Looking briefly into the driver I found third scenario — no resource at all.
table for more stricter rules.
written ACPI tables) driver needs such.
> Do you have a suggestion as to how to write ACPI tables to avoid the issue?
1. Allocate new ID and use it (perhaps not the best path).
Dmitry Torokhov - Feb. 7, 2019, 8:29 p.m.
> >> > > does not try to parse GpioInt() resources.
> >> And why is this a problem?
> Looking briefly into the driver I found third scenario — no resource at all.
> table for more stricter rules.
No, no DMI rules please, they are more pain than anything.
> written ACPI tables) driver needs such.
This is simply kicking the can down the road.
we need to improve it if we see devices with multiple interrupts.
Mika Westerberg - Feb. 11, 2019, 10:30 a.m.
> > 2. Use GPE(s).
> we need to improve it if we see devices with multiple interrupts.
Hans de Goede - Feb. 11, 2019, 3:42 p.m.
>> we need to improve it if we see devices with multiple interrupts.
as soon as that is the case then the meaning of index becomes ambiguous.
Gpio or a GpioInt; or in this case if they want an Interrupt or a GpioInt.
+	 * as a last resort.
user
There are one hundred and sixty-nine "o"s.
assistant