linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: acourbot@nvidia.com (Alexandre Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] gpiolib: remove gpiochip_reserve()
Date: Sat,  2 Feb 2013 23:44:04 +0900	[thread overview]
Message-ID: <1359816246-3979-1-git-send-email-acourbot@nvidia.com> (raw)

The Tosa (Sharp SL-C6000x) target is the last remaining user of
gpiochip_reserve(). I would like to get rid of this function as part of my
project to totally remove the big static gpio_desc[] array of gpiolib. Patches
that achieve this are written and working, but the presence of
gpiochip_reserve() makes it necessary to maintain a list of "reserved" ranges
in the GPIO space, which complexifies code that would be much simpler
otherwise.

Even for Tosa the use of gpiochip_reserve() does not seem necessary - all GPIO
controllers have their own base GPIO set AFAICT, so there should be no need to
use it. And without any user in the kernel, there should be no reason to keep
this function.

If Dmitri could give his Acked-by or Tested-by and one of the GPIO maintainers
merge this series, I could go ahead with the deeper changes to gpiolib.

Thanks,

Alexandre Courbot (2):
  arm: pxa: tosa: do not use gpiochip_reserve()
  gpiolib: remove gpiochip_reserve()

 arch/arm/mach-pxa/tosa.c   |  6 -----
 drivers/gpio/gpiolib.c     | 58 +++++++---------------------------------------
 include/asm-generic/gpio.h |  1 -
 3 files changed, 8 insertions(+), 57 deletions(-)

-- 
1.8.1.1

             reply	other threads:[~2013-02-02 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02 14:44 Alexandre Courbot [this message]
2013-02-02 14:44 ` [PATCH 1/2] arm: pxa: tosa: do not use gpiochip_reserve() Alexandre Courbot
2013-02-03  0:29   ` Haojian Zhuang
2013-02-04 20:42     ` Linus Walleij
2013-02-02 14:44 ` [PATCH 2/2] gpiolib: remove gpiochip_reserve() Alexandre Courbot
2013-02-02 15:01 ` [PATCH 0/2] " Linus Walleij

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=1359816246-3979-1-git-send-email-acourbot@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).