linux-kernel - Re: [PATCH] drivers: misc: add gpio wakeup driver

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: <CACRpkdbeHco4iykPeH=NF3hWzWm3UxfAaaTvM4y74NfSbJi2Jw@mail.gmail.com>
Date:	Tue, 15 Oct 2013 23:35:03 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Daniel Mack <zonque@...il.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Mark Brown <broonie@...nel.org>,
	Stephen Warren <swarren@...dotorg.org>
Subject: Re: [PATCH] drivers: misc: add gpio wakeup driver

On Tue, Oct 15, 2013 at 9:32 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Friday 11 October 2013, Linus Walleij wrote:

>> It *may* be that we have many GPIO drivers that do not accept
>> that you request an interrupt on them before you have done
>> request_gpio() followed by gpio_to_irq() on the pin. Then this
>> shall be treated like a bug and the GPIO driver fixed to handle
>> this. (That was the outcome of this discussion.)
>
> I haven't followed that discussion, but it's good to hear that
> you made some progress there. I find it a bit worrying that you
> say the behavior may be dependent on the gpio driver, but maybe
> I didn't fully understand what the resolution is.

It's some consensus on how to do this, but the existing drivers
need to be augmented to implement it according to that
consensus, especially those using device tree.

If noone else helps I guess it goes on top of the pile of stuff
for the GPIO maintainer to fix...

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/