From: Jonathan Cameron <jic23@kernel.org>
To: Leed Aguilar <leed.aguilar@ti.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] staging:iio:magnetometer:ak8975: use gpio_request_one api
Date: Fri, 01 Jun 2012 09:01:47 +0100 [thread overview]
Message-ID: <4FC876EB.7090701@kernel.org> (raw)
In-Reply-To: <1338470231-19272-1-git-send-email-leed.aguilar@ti.com>
On 5/31/2012 2:17 PM, Leed Aguilar wrote:
> Use gpio_request_one api, it looks cleaner.
But adds a dependency on GPIOLIB. I'm not that bothered by
that but it needs to be explicit in the Kconfig.
>
> Signed-off-by: Leed Aguilar<leed.aguilar@ti.com>
> Cc: Jonathan Cameron<jic23@kernel.org>
> ---
> drivers/staging/iio/magnetometer/ak8975.c | 10 +---------
> 1 files changed, 1 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/iio/magnetometer/ak8975.c b/drivers/staging/iio/magnetometer/ak8975.c
> index ebc2d08..52833cd 100644
> --- a/drivers/staging/iio/magnetometer/ak8975.c
> +++ b/drivers/staging/iio/magnetometer/ak8975.c
> @@ -487,21 +487,13 @@ static int ak8975_probe(struct i2c_client *client,
> /* We may not have a GPIO based IRQ to scan, that is fine, we will
> poll if so */
> if (gpio_is_valid(eoc_gpio)) {
> - err = gpio_request(eoc_gpio, "ak_8975");
> + err = gpio_request_one(eoc_gpio, GPIOF_IN, "ak_8975");
> if (err< 0) {
> dev_err(&client->dev,
> "failed to request GPIO %d, error %d\n",
> eoc_gpio, err);
> goto exit;
> }
> -
> - err = gpio_direction_input(eoc_gpio);
> - if (err< 0) {
> - dev_err(&client->dev,
> - "Failed to configure input direction for GPIO %d, error %d\n",
> - eoc_gpio, err);
> - goto exit_gpio;
> - }
> }
>
> /* Register with IIO */
prev parent reply other threads:[~2012-06-01 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 13:17 [PATCH v2] staging:iio:magnetometer:ak8975: use gpio_request_one api Leed Aguilar
2012-06-01 8:01 ` Jonathan Cameron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC876EB.7090701@kernel.org \
--to=jic23@kernel.org \
--cc=leed.aguilar@ti.com \
--cc=linux-iio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.