From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lubomir Popov Date: Fri, 21 Jun 2013 15:29:00 +0300 Subject: [U-Boot] [PATCH] ARM: OMAP: GPIO: Fix valid range and enable usage of all GPIOs on OMAP5 In-Reply-To: <1371812065.25258.1.camel@phoenix> References: <1371812065.25258.1.camel@phoenix> Message-ID: <51C4470C.5030107@mm-sol.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 > --- > 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