From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-acpi@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpiolib: Forbid irqchip default trigger for ACPI enumerated devices
Date: Thu, 24 Nov 2016 09:59:25 +0200 [thread overview]
Message-ID: <20161124075925.GD1476@lahna.fi.intel.com> (raw)
In-Reply-To: <3728863.ohrj1SkIMB@vostro.rjw.lan>
On Thu, Nov 24, 2016 at 02:33:55AM +0100, Rafael J. Wysocki wrote:
> On Monday, September 12, 2016 02:29:51 PM Mika Westerberg wrote:
> > Follow DT and forbid default trigger if the GPIO irqchip device is
> > enumerated from ACPI. Triggering for these devices will be configured
> > automatically from ACPI interrupt resources provided by the BIOS.
> >
> > Suggested-by: Linus Walleij <linus.walleij@linaro.org>
> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > ---
> > This is on top of Marc's patch here:
> >
> > https://lkml.org/lkml/2016/9/7/121
> >
> > drivers/gpio/gpiolib.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index 5707b5d12b28..0efb67f387ea 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -1618,13 +1618,18 @@ int _gpiochip_irqchip_add(struct gpio_chip *gpiochip,
> > of_node = gpiochip->of_node;
> > #endif
> > /*
> > - * Specifying a default trigger is a terrible idea if DT is
> > + * Specifying a default trigger is a terrible idea if DT or ACPI is
> > * used to configure the interrupts, as you may end-up with
> > * conflicting triggers. Tell the user, and reset to NONE.
> > */
> > if (WARN(of_node && type != IRQ_TYPE_NONE,
> > "%s: Ignoring %d default trigger\n", of_node->full_name, type))
> > type = IRQ_TYPE_NONE;
> > + if (has_acpi_companion(gpiochip->parent) && type != IRQ_TYPE_NONE) {
> > + acpi_handle_warn(ACPI_HANDLE(gpiochip->parent),
> > + "Ignoring %d default trigger\n", type);
> > + type = IRQ_TYPE_NONE;
> > + }
> >
> > gpiochip->irqchip = irqchip;
> > gpiochip->irq_handler = handler;
> >
>
> Has this gone anywhere already?
Yes, it should be in the mainline kernel with commit id
0a1e005374910180c30247386992565b05109eac.
next prev parent reply other threads:[~2016-11-24 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 11:29 [PATCH] gpiolib: Forbid irqchip default trigger for ACPI enumerated devices Mika Westerberg
2016-11-24 1:33 ` Rafael J. Wysocki
2016-11-24 7:59 ` Mika Westerberg [this message]
2016-11-24 13:45 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161124075925.GD1476@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.