[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201102211207.29291.alexander.stein@systec-electronic.com>
Date: Mon, 21 Feb 2011 12:07:27 +0100
From: Alexander Stein <alexander.stein@...tec-electronic.com>
To: Wolfram Sang <w.sang@...gutronix.de>
Cc: "Lars-Peter Clausen" <lars@...afoo.de>,
Eric Miao <eric.y.miao@...il.com>,
Peter Tyser <ptyser@...-inc.com>, linux-kernel@...r.kernel.org,
Alek Du <alek.du@...el.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
David Brownell <dbrownell@...rs.sourceforge.net>,
"Uwe Kleine-K?nig" <u.kleine-koenig@...gutronix.de>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Joe Perches <joe@...ches.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH v2 1/4] gpiolib: Add "unknown" direction support
On Monday 21 February 2011, 10:47:56 Wolfram Sang wrote:
> > We had exported our 5V_enable gpio to sysfs to allow a user-space
> > application to enable/disable devices connected to 5V circuit.
> > But on the other hand we had to read the current status of this gpio in
> > the power-fail interrupt handler to distinguish between false-positive
> > (5V disabled) and a correct detection.
>
> What about gpio_export() (description in Documentation/gpio.txt)?
Ah, I didn't know about this. I just expected this is only used from sysfs
part. But you have to make sure your .ko is loaded before userspace is
accessing sysfs and tries to export the GPIO.
Or is it "allowed" by the API convention to gpio_request and gpio_export (and
set direction) a GPIO in the machine startup code which will later be used in
a different place?
Alexander
--
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/
Powered by blists - more mailing lists