From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Mon, 15 Feb 2016 18:40:38 +0100
Subject: [U-Boot] [PATCH] gpio: Add DM GPIO driver for Marvell MVEBU
In-Reply-To: <56C20734.3010402@elecsyscorp.com>
References: <1455281210-5739-1-git-send-email-sr@denx.de>
 <56C20734.3010402@elecsyscorp.com>
Message-ID: <56C20D96.2060504@denx.de>
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 Kevin,

On 15.02.2016 18:13, Kevin Smith wrote:
> On 02/12/2016 06:46 AM, Stefan Roese wrote:
>> This patch adds a DM GPIO driver for the Marvell MVEBU SoCs. There are
>> other non-DM drivers that might be used on these platforms. But this
>> patch creates a new DM driver. Which will be used by all Armada XP/38x
>> boards. Other MVEBU SoC (Kirkwood / Orion) may follow once they
>> support DM as well.
>>
> Are there any GPIO functions on the db-88f6820-gp board that I can use
> to test this patch?  I'm not seeing any "xxxx-gpios = <&gpioX ...>"
> nodes in the current device tree.

Correct. But there are the GPIO controller DT nodes. That will
instantiate the GPIO DM interface. So you could use:

=> dm tree

to see the GPIO controllers listed (if enabled). And if you enable
the GPIO commands (CONFIG_CMD_GPIO) then you can e.g. do:

=> gpio status -a

to list all GPIOs and there status. If a board / driver claims a
GPIO (request_gpio) this should also be visible via this interface.

Thanks,
Stefan