All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Drivers <Drivers@analog.com>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] IIO: ADC: New driver for AD7606/AD7606-6/AD7606-4
Date: Wed, 09 Feb 2011 11:06:30 +0000	[thread overview]
Message-ID: <4D527536.8040602@cam.ac.uk> (raw)
In-Reply-To: <4D52505A.50803@analog.com>

<snip>
>>>
>>> +config AD7606
>>> +     tristate "Analog Devices AD7606 ADC driver"
>>> +     depends on GPIOLIB
>>>     
>> Is that the correct depend?  I think we need Generic GPIO but it is at least
>> in theary posible to have that without GPIOLIB.
>>   
> Well - before I utilized gpio_request_one() and friends the dependency
> was on GENERIC_GPIO.
> However  gpio_request_one() is defined as a function only in gpiolib,
> there could have been inline
> replacements in case of !GPIOLIB, but unfortunately thats not the case.
Ah fair enough. I guess these will only move into GENERIC_GPIO if someone
needs them on a board that isn't using GPIOLIB.


  reply	other threads:[~2011-02-09 11:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 13:29 [PATCH] IIO: ADC: New driver for AD7606/AD7606-6/AD7606-4 michael.hennerich
2011-02-08 19:36 ` Jonathan Cameron
2011-02-09  8:29   ` Michael Hennerich
2011-02-09 11:06     ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-22 20:46 michael.hennerich
2011-02-10  8:28 michael.hennerich
2011-02-09 12:07 michael.hennerich
2011-02-03 14:51 michael.hennerich
2011-02-03 20:37 ` Jonathan Cameron
2011-02-03 20:42   ` Jonathan Cameron
2011-02-04 13:48   ` Hennerich, Michael
2011-02-04 14:51     ` Jonathan Cameron
2011-02-04 15:07       ` Hennerich, Michael
2011-02-04 15:45         ` Jonathan Cameron
2011-02-04 14:27   ` Hennerich, Michael
2011-02-04 14:56     ` Jonathan Cameron

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=4D527536.8040602@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Drivers@analog.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    /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.