[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinq98+ryOOKx1o1o21x9VnHz3nRCHh=5Wwixn4o@mail.gmail.com>
Date: Tue, 7 Sep 2010 21:13:12 +0200
From: "avictor.za@...il.com" <avictor.za@...il.com>
To: David Brownell <david-b@...bell.net>
Cc: Eric Miao <eric.y.miao@...il.com>,
Ryan Mallon <ryan@...ewatersys.com>,
Nicolas Ferre <nicolas.ferre@...el.com>,
linux-kernel@...r.kernel.org, bn@...sdigital.com,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] pio: add arch specific gpio_is_valid() function
hi,
> NAK still. You're trying to abuse gpio_is_valid(),
> which I see no need to support.
>
> In terms of GPIO framework architecture, zero is
> the first GPIO in all cases, and is always
> a valid GPIO number, even if it's not
> requestable/swritable/readable on a given board.
>
> Whether it's usable on a given platform depends
> on whether a GPIO controller is registered which
> claims numbers 0..N ... (assuming gpiolib in use).
How should the following be done in a driver then?
if (gpio_is_valid(device->output_pin)) {
if (gpio_request(device->output_pin, "driverX") != 0)
goto error_handling;
/* continue with gpio setup */
}
else {
/* there is no vcc_pin, so don't do any gpio setup */
}
....
if (gpio_is_valid(device->output_pin)) {
/* set value high */
}
Regards,
Andrew Victor
--
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