From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multiplatform: Sort the max gpio numbers.
Date: Mon, 11 Mar 2013 16:38:42 +0000 [thread overview]
Message-ID: <20130311163842.GK4977@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1359890688-10336-1-git-send-email-maxime.ripard@free-electrons.com>
Arnd, Olof,
Have you merged this for -rc ?
On Sun, Feb 03, 2013 at 12:24:48PM +0100, Maxime Ripard wrote:
> When building a multiplatform kernel, we could end up with a smaller
> number of GPIOs than the one required by the platform the kernel was
> running on.
>
> Sort the max GPIO number by descending order so that we always take the
> highest number required.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
> arch/arm/Kconfig | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 1e86fa9..852ae76 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1626,13 +1626,16 @@ config LOCAL_TIMERS
> accounting to be spread across the timer interval, preventing a
> "thundering herd" at every timer tick.
>
> +# The GPIO number here must be sorted by descending number. In case of
> +# a multiplatform kernel, we just want the highest value required by the
> +# selected platforms.
> config ARCH_NR_GPIO
> int
> default 1024 if ARCH_SHMOBILE || ARCH_TEGRA
> - default 355 if ARCH_U8500
> - default 264 if MACH_H4700
> default 512 if SOC_OMAP5
> + default 355 if ARCH_U8500
> default 288 if ARCH_VT8500 || ARCH_SUNXI
> + default 264 if MACH_H4700
> default 0
> help
> Maximum number of GPIOs in the system.
> --
> 1.7.10.4
>
next prev parent reply other threads:[~2013-03-11 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 11:24 [PATCH] ARM: multiplatform: Sort the max gpio numbers Maxime Ripard
2013-03-11 16:38 ` Russell King - ARM Linux [this message]
2013-03-11 20:51 ` Arnd Bergmann
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=20130311163842.GK4977@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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