From: Lubomir Popov <lpopov@mm-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: OMAP: GPIO: Fix valid range and enable usage of all GPIOs on OMAP5
Date: Fri, 21 Jun 2013 15:29:00 +0300 [thread overview]
Message-ID: <51C4470C.5030107@mm-sol.com> (raw)
In-Reply-To: <1371812065.25258.1.camel@phoenix>
Hi Axel,
On 21/06/13 13:54, Axel Lin wrote:
> The omap_gpio driver is used by AM33XX, OMAP3/4, OMAP54XX and DRA7XX SoCs.
> These SoCs have different gpio count but currently omap_gpio driver uses hard
> coded 192 which is wrong.
>
> This patch fixes this issue by:
> 1. Move define of OMAP_MAX_GPIO to all arch/arm/include/asm/arch-omap*/gpio.h.
> 2. Update gpio bank settings and enable GPIO modules 7 & 8 clocks for OMAP5.
>
> Thanks for Lubomir Popov to provide valuable comments to fix this issue.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> This patch supersedes below patches:
>
> [PATCH v3 1/2] gpio: omap_gpio: Fix valid gpio range for AM33XX [1]
> [PATCH v3 2/2] gpio: omap_gpio: Fix valid GPIO range for OMAP5 [2]
> [PATCH 1/2] OMAP5: Fix gpio_bank_54xx setting [3]
> [PATCH 2/2] OMAP: gpio: Introduce get_omap_gpio_count() function to get gpio count [4]
>
Applied and tested on a custom OMAP5430 board with some GPIOs from banks 7 & 8. Works OK.
Tested-by: Lubomir Popov <lpopov@mm-sol.com>
next prev parent reply other threads:[~2013-06-21 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 10:54 [U-Boot] [PATCH] ARM: OMAP: GPIO: Fix valid range and enable usage of all GPIOs on OMAP5 Axel Lin
2013-06-21 12:29 ` Lubomir Popov [this message]
2013-06-24 19:34 ` Heiko Schocher
2013-07-02 20:07 ` [U-Boot] " Tom Rini
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=51C4470C.5030107@mm-sol.com \
--to=lpopov@mm-sol.com \
--cc=u-boot@lists.denx.de \
/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