public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] gpio / ACPI: ignore GpioInt() GPIOs when requesting GPIO_OUT_*
Date: Thu, 31 Mar 2016 10:33:34 -0700	[thread overview]
Message-ID: <20160331173334.GA39098@dtor-ws> (raw)
In-Reply-To: <CACRpkdYxpP=tKhuWyCQT4FdkEeruPS-0DWbJmXmPMFkVye=9tA@mail.gmail.com>

On Thu, Mar 31, 2016 at 11:49:13AM +0200, Linus Walleij wrote:
> On Thu, Mar 24, 2016 at 6:50 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> 
> > From: Dmitry Torokhov <dtor@chromium.org>
> >
> > When firmware does not use _DSD properties that allow properly name GPIO
> > resources, the kernel falls back on parsing _CRS resources, and will
> > return entries described as GpioInt() as general purpose GPIOs even
> > though they are meant to be used simply as interrupt sources for the
> > device:
> 
> Patch applied for fixes. Is this a regression so that I should
> also tag it for stable?

No, I think it is OK to keep it in 4.6+.

Thanks.

-- 
Dmitry

      reply	other threads:[~2016-03-31 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 17:50 [PATCH v2] gpio / ACPI: ignore GpioInt() GPIOs when requesting GPIO_OUT_* Dmitry Torokhov
2016-03-31  9:49 ` Linus Walleij
2016-03-31 17:33   ` Dmitry Torokhov [this message]

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=20160331173334.GA39098@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox