public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Courbot <acourbot@nvidia.com>
To: Christian Ruppert <christian.ruppert@abilis.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arch <linux-arch@vger.kernel.org>,
	Pierrick Hascoet <pierrick.hascoet@abilis.com>,
	sascha leuenberger <sascha.leuenberger@abilis.com>
Subject: Re: [PATCH v2 0/4] remove GENERIC_GPIO
Date: Tue, 16 Apr 2013 11:27:41 +0900	[thread overview]
Message-ID: <516CB71D.9070603@nvidia.com> (raw)
In-Reply-To: <20130415074322.GC3264@ab42.lan>

On 04/15/2013 04:43 PM, Christian Ruppert wrote:
> Hello Alexandre,
>
> On Fri, Apr 12, 2013 at 11:42:42AM -0700, Alexandre Courbot wrote:
>> Hi Vineet,
>>
>> On Thu, Apr 11, 2013 at 7:05 AM, Vineet Gupta
>> <Vineet.Gupta1@synopsys.com> wrote:
>>> I'm the maintainer for arch/arc.
>>>
>>> For 3.10, we are going to have a sub-platform included which enables GPIO.
>>> However given that your patch is still not in a maintainer tree I'm going to apply
>>> the platform patch with GENERIC_GPIO and it would show up in -next as well. But
>>> don't be alarmed - to align with your work, Christian or you can then possibly
>>> apply a patch to make arch/arc/* confirm to your work - preferably via your
>>> tree/patchseries  - OK ?
>>
>> I guess that would work, but since I assume your platforms' GPIO
>> implementation use gpiolib anyway wouldn't it be simpler and more
>> logical to directly require it?
>>
>> If you have reasons for not doing so I'm ok with doing the switch
>> later too, anyway that's what I had to do for all the other archs.
>
> The GPIO driver patch was proposed on lkml a few days ago and although I
> am not aware of any "GENERIC" methods it uses it does not compile
> without GENERIC_GPIO being defined (errors in of_gpio.h etc). You can
> review the patch at https://lkml.org/lkml/2013/4/10/385.
>
> We'd be happy to accept any guidance on how to remove GENERIC_GPIO.
> Also, I'm not sure the custom interface to the pin controller is a great
> solution and suggestions are welcome. The goal is to remove redundancy
> between the drivers in the definition of pin groups.

Hi Christian,

Thanks for the link to the patch. This is rather puzzling - in 
drivers/gpio/Kconfig your GPIO_TB10X config option seems to be under the 
"if GPIOLIB" condition which is what I expect, since your driver uses 
gpiolib. If you go to the GPIOLIB config option, you notice that is 
explicitly selects GENERIC_GPIO as a result of being enabled. Therefore 
CONFIG_GENERIC_GPIO should always be defined whenever your driver is 
compiled and it should not be needed to select it elsewhere. Do we agree 
on that?

I'd really like to go to the bottom of this since I saw several similar 
issues already, but I don't understand how this can happen at all. 
Having the .config of both the working (with GENERIC_GPIO selected) and 
non-working (only GPIOLIB selected) cases would probably be helpful, 
could you send them to me?

Thanks,
Alex.

  reply	other threads:[~2013-04-16  2:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 18:32 [PATCH v2 0/4] remove GENERIC_GPIO Alexandre Courbot
2013-04-08 18:32 ` [PATCH v2 1/4] gpio: convert selectors of GENERIC_GPIO to GPIOLIB Alexandre Courbot
2013-04-16  9:34   ` Grant Likely
2013-04-16  9:34     ` Grant Likely
2013-04-08 18:32 ` [PATCH v2 2/4] gpio: remove GENERIC_GPIO config option Alexandre Courbot
2013-04-16  9:33   ` Grant Likely
2013-04-16  9:33     ` Grant Likely
2013-04-08 18:32 ` [PATCH v2 4/4] gpio: update gpio Chinese documentation Alexandre Courbot
2013-04-16  9:40   ` Grant Likely
2013-04-16  9:40     ` Grant Likely
2013-04-11 14:05 ` [PATCH v2 0/4] remove GENERIC_GPIO Vineet Gupta
2013-04-12 18:42   ` Alexandre Courbot
2013-04-15  7:43     ` Christian Ruppert
2013-04-16  2:27       ` Alex Courbot [this message]
2013-04-16  7:34         ` Christian Ruppert
2013-04-16  9:01           ` Alex Courbot
2013-04-16  9:32 ` Grant Likely
2013-04-16  9:32   ` Grant Likely
2013-04-16  9:45   ` Grant Likely
2013-04-16 22:11     ` Alexandre Courbot
2013-04-16 22:11       ` Alexandre Courbot
     [not found] ` <1365445950-5736-4-git-send-email-gnurou@gmail.com>
2013-04-16  9:39   ` [PATCH v2 3/4] gpio: rename CONFIG_GPIOLIB to CONFIG_GPIO Grant Likely
2013-04-16  9:39     ` Grant Likely

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=516CB71D.9070603@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=christian.ruppert@abilis.com \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=pierrick.hascoet@abilis.com \
    --cc=sascha.leuenberger@abilis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox