linux-kernel - Re: [patch 2.6.27-rc7] gpiolib: request/free hooks

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aec7e5c30809282048x3d9a201j12303091e9d93a49@mail.gmail.com>
Date:	Mon, 29 Sep 2008 12:48:02 +0900
From:	"Magnus Damm" <magnus.damm@...il.com>
To:	"David Brownell" <david-b@...bell.net>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [patch 2.6.27-rc7] gpiolib: request/free hooks

On Sun, Sep 28, 2008 at 3:29 AM, David Brownell <david-b@...bell.net> wrote:
> On Saturday 27 September 2008, Magnus Damm wrote:
>>
>> Looking good. I'm currently hacking on some pinmuxed gpio code for
>> SuperH, and I'd like to use these request/free callbacks to select
>> proper pinmux state.
>
> I'm not so keen on that particular overloading, but I can
> understand why it might be wanted on systems which have a
> happy one-to-one mapping between GPIOs and pins.

Hm, sounds like you prefer to keep pinmuxing and GPIO code separated?

> If you do that, be ready to provide a pinmux-only interface
> at some point when this "piggybacking" breaks something...

In the SuperH case GPIO pin direction selection is done in the same
way as selecting pin function. So in and out directions can be seen as
two pin functions. And since we want to support GPIO pin direction we
may as well support setting pin functions as well.

But maybe there are better ways to integrate it, I'm not sure.

>> > --- a/drivers/gpio/gpiolib.c
>> > +++ b/drivers/gpio/gpiolib.c
>> > @@ -781,6 +785,7 @@ EXPORT_SYMBOL_GPL(gpiochip_remove);
>> >  int gpio_request(unsigned gpio, const char *label)
>> >     ...
>>
>> The code above doesn't catch double gpio_request() user calls
>> properly. Or rather, the user will receive an error but the
>> chip->request() callback may get called twice.
>>
>> What about modifying the gpiolib code to handle that? I think that
>> sounds like a better idea than cover ing that case in the chip code...
>
> Yeah.  Better to test-and-set the flag and then request, and backout
> if it fails, than the other way.  Just who wrote that crap in the
> first place?  Sigh.  (Notice it's done that way already in the code
> path handling implicit requesting ... )

Sounds good.

> I'll send an updated patch along soonish.

Thank you!

/ magnus
--
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/