All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: kconfig: make max8973 driver to depend on GPIOLIB
Date: Thu, 9 Apr 2015 15:31:09 +0530	[thread overview]
Message-ID: <55264DE5.4050508@nvidia.com> (raw)
In-Reply-To: <20150408164323.GA6023@sirena.org.uk>

On Wednesday 08 April 2015 10:13 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Apr 08, 2015 at 07:07:07PM +0530, Laxman Dewangan wrote:
>> MAX8973 regulator driver uses the GPIO APIs for accessing the
>> control signal connected to its pin from host processor.
>>
>> Make this driver depends on GPIOLIB.
> The GPIO usage in the driver appears to be optional, it handles the GPIO
> not being controllable.  This suggests to me that the gpiolib dependency
> shouldn't be required and that it would be better to fix this by
> ensuring that all the gpiolib functions being used have appropriate
> stubs.  Which ones are causing problems?
>

Thanks for review.

Sometime ago, I got the comiplation error on random config for one of 
architecture which was not having GPIO architecture. The compilation 
error was reported on tps62360-regulator.c which is also using similar 
i2c calls.

So to avoid similar issue, I make this depends on GPIOLIB.

However, I looked gpio.h and it has all required APIs as static inline 
if GPIOLIB is not there so atleast compilation issue will not be there.

Now going through code, I think if gpios are not there then also it 
should work.
Not tested this on my board as I can not boot without gpio.

I think we can drop this patch.

Thanks,
Laxman


      reply	other threads:[~2015-04-09 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 13:37 [PATCH] regulator: kconfig: make max8973 driver to depend on GPIOLIB Laxman Dewangan
2015-04-08 16:43 ` Mark Brown
2015-04-09 10:01   ` Laxman Dewangan [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=55264DE5.4050508@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@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.