From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ajay Bhargav <ajay.bhargav@einfochips.com>
Date: Tue, 19 Jul 2011 15:59:07 +0530 (IST)
Subject: [U-Boot] [PATCH 1/4] gpio: Adds GPIO driver support for
	Armada100
In-Reply-To: <550445252.29883.1311070783386.JavaMail.root@ahm.einfochips.com>
Message-ID: <356527245.29929.1311071347338.JavaMail.root@ahm.einfochips.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Prafulla,

> I checked datasheet and for most GPIOs, AF1 is given as GPIO but for few
> its not, so adding a glue logic to check for specific GPIOs wont be a good idea.
> That's the reason i thought its good to keep MFP out of this. Please give suggestions.

correcting my previous message, I meant AF0.
adding to this.. I checked Linux kernel source and they are simply validating if gpio number
is within max limits so request returns 0.

And you told me to use MAX_MFP instead of using ARMD_MAX_GPIO, but MAX_MFP is defined lesser
than the actual number of GPIO e.g. in case of armada100 MAX_MFP is defined 117 whereas max
GPIOs are around 123.

Please give me some suggestion.

Regards,
Ajay Bhargav