From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Tue, 18 Jun 2019 12:33:35 +0200
Subject: [U-Boot] [PATCH v3 3/5] ARM: dm: mxs: gpio: Add support for
 DM/DTS in the mxs_gpio.c driver (DM_GPIO)
In-Reply-To: <20190618085706.162ed81e@jawa>
References: <20190615223442.12246-1-lukma@denx.de>
 <20190615223442.12246-4-lukma@denx.de>
 <1c07bf95-8a43-6a5b-3e22-31cd4cd0b811@denx.de> <20190617103737.0bee7dc3@jawa>
 <f0a7ac08-acb8-77b7-3f3b-c2436828c561@denx.de> <20190617150137.7e6500c5@jawa>
 <26174e32-2b03-f8b4-a7a3-124f9fbdf90d@denx.de> <20190618085706.162ed81e@jawa>
Message-ID: <77ead1b0-0e64-6bf8-245f-5eb153fa6fe6@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

On 6/18/19 8:57 AM, Lukasz Majewski wrote:

[...]

> To have a consensus regarding the gpio-ranges and mxs_gpio - here is
> my proposition:
> 
> 1. I can provide "gpio-ranges" properties to imx28-u-boot.dtsi
> 
> With support similar to one from drivers/gpio/gpio-rcar.c, which only
> extracts the info regarding pin mapping, but omits the phandle for
> pinmux (pinmux will not be supported).
> 
> 2. I will not upstream those properties to Linux (and adjust the
> working mxs gpio driver in any way) - they would be only U-Boot specific

Why not ?

> 3. The IMX_GPIO_NR() macro will not be defined for i.MX28 GPIO.
> 
> 4. Considering point 3 - all converted boards will have to use dm_gpio*
> API.

That's good.

-- 
Best regards,
Marek Vasut