On Wed, 2017-11-08 at 21:45 +0100, Linus Walleij wrote:
> On Wed, Nov 8, 2017 at 6:03 PM, Mika Westerberg
> <mika.westerberg@xxxxxxxxxxxxxxx> wrote:
> > On Wed, Nov 08, 2017 at 06:35:46PM +0200, Andy Shevchenko wrote:
> > > +Cc: Mika
> > One idea is to allow this strict mode to be relaxed by drivers
> > perhaps
> > by passing quirks through struct acpi_gpio_mapping:
> >
> > static const struct acpi_gpio_mapping acpi_foo_gpios[] = {
> > /*
> > * This platform has a bug in ACPI GPIO description making
> > IRQ
> > * GPIO to be output only. Ask the GPIO core to ignore this
> > * limit.
> > */
> > { "foobar-gpios", &foobar_gpios, 1,
> > ACPI_QUIRK_IGNORE_IO_RESTRICTION },
> > {},
> > };
> >
> > or something like that. Not sure if I missed something obvious,
> > though.
>
> This looks like an elegant solution to me.
>
> Can it be done?
I have sent today a series against GPIO ACPI library to support quirks
in general.
P.S. Just realized I forgot to put Suggested-by tag there.
--
Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
