From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: ixp4xx, u300: Select ARCH_REQUIRE_GPIOLIB, not GENERIC_GPIO
Date: Mon, 05 Sep 2011 08:54:30 +0200 [thread overview]
Message-ID: <87r53v7a3d.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <1315192383.3092.260.camel@deadeye> (Ben Hutchings's message of "Mon, 05 Sep 2011 04:12:56 +0100")
Ben Hutchings <ben@decadent.org.uk> writes:
Hi,
> The GPIO implementations for these two machines depend on gpiolib,
> so they must not select GENERIC_GPIO directly.
They're not calling gpiochip_add afaik so they should really only select
GENERIC_GPIO.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> This hould fix the build failure seen here:
> https://buildd.debian.org/status/fetch.php?pkg=linux-2.6&arch=armel&ver=3.1.0%7Erc4-1%7Eexperimental.1&stamp=1315007168
The problem here is that gpio_request_one has been added to the ads7846
driver but gpio_request_one is not defined in GENERIC_GPIO case (I
guess that other (arm and non-arm) platforms may hit similar troubles
with gpio_request_one. One quick fix would be to add a gpio_request_one
function say in asm-generic/gpio.h. One other fix would be to define
gpio_request_one and gpio_request_array in each
machine/platform/... specific header. Don't know what's the best
solution.
Arnaud
next prev parent reply other threads:[~2011-09-05 6:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 3:12 [PATCH] arm: ixp4xx, u300: Select ARCH_REQUIRE_GPIOLIB, not GENERIC_GPIO Ben Hutchings
2011-09-05 6:54 ` Arnaud Patard (Rtp) [this message]
2011-09-05 10:41 ` Russell King - ARM Linux
2011-09-05 12:18 ` Arnaud Patard (Rtp)
2011-09-05 12:49 ` [RFC/PATCH] ARM: ixp4xx gpiolib support Imre Kaloz
2011-09-06 6:49 ` Arnaud Patard (Rtp)
2011-09-06 7:30 ` Uwe Kleine-König
2011-09-05 12:41 ` [PATCH] arm: ixp4xx, u300: Select ARCH_REQUIRE_GPIOLIB, not GENERIC_GPIO Linus Walleij
2011-09-05 16:22 ` Ben Hutchings
2011-09-06 7:26 ` 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=87r53v7a3d.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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 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.