lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160331173334.GA39098@dtor-ws>
Date:	Thu, 31 Mar 2016 10:33:34 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] gpio / ACPI: ignore GpioInt() GPIOs when requesting
 GPIO_OUT_*

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@...il.com> wrote:
> 
> > From: Dmitry Torokhov <dtor@...omium.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ