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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 8 Jan 2010 17:08:28 +1100
From:	Ben Nizette <>
To:	Eric Miao <>
Cc:	David Brownell <>,
	linux-kernel <>,
	Andrew Morton <>
Subject: Re: [PATCH] gpio: introduce gpio_request_one() and friends

On 08/01/2010, at 4:14 PM, Eric Miao wrote:

> commit 29cd35f57699fd93a12132186d52109a55ed57e7
> Author: Eric Miao <>
> Date:   Fri Jan 8 12:16:28 2010 +0800
>    gpio: introduce gpio_request_one() and friends
>    gpio_request() without initial configuration of the GPIO is normally
>    useless, introduce gpio_request_one() together with GPIOF_ flags for
>    input/output direction and initial output level.

Well yea it is useless without initial configuration but I've always done that configuration before any gpiolib calls.  The initial direction and state stuff really has to be set up and pin-mux or gpio-chip-activate time otherwise it'll glitch; by the time we get to gpio_request time I've got everything just how I like it and just want the refcount aspect of gpio_request.

I'm obviously thinking in a very small-minded platform-gpio-only kind of a way, what system have you got which uses this (and how does it not glitch)?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists