[U-Boot] [PATCH 00/11] Add GPIO driver for Freescale Vybrid platform

[Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>]

Hello,

On 05/26/2015 04:57 PM, Stefano Babic wrote:
> Hi,
>
> On 24/05/2015 21:34, Bhuvanchandra DV wrote:
>> Hello Stefano,
>>
>> On 05/18/2015 06:36 PM, Bhuvanchandra DV wrote:
>>> This patch-set adds GPIO driver, DSPI and device tree support
>>> for Freescale Vybrid platform and Toradex Colibri Vybrid VF50,
>>> VF61 modules.
>>>
>>> Following cases are tested with Vybrid GPIO driver:
>>> - with DM, without DT
>>> - with DM and DT
>>> Both the above cases were tested on Toradex Colibri Vybrid VF50, VF61
>>> modules and both works fine.
>>>
>>> - The patchset is based and tested on the latest master branch.
>>>
>>> Bhuvanchandra DV (9):
>>>     dm: gpio: uclass: Add flag to control sequence numbering
>>>     dm: gpio: vf610: Add GPIO driver support
>>>     colibri_vf: Add pinmux entries for GPIOs
>>>     colibri_vf: Enable GPIO support
>>>     arm: vf610: Add clock support for DSPI
>>>     arm: vf610: Add iomux support for DSPI
>>>     vf610: dts: Add device tree support
>>>     colibri-vf: Enable SPI support
>>>     colibri_vf: Add separate defconfig for device tree support
>>>
>>> Sanchayan Maity (2):
>>>     usb: ehci-vf: Add weak function for board specific initialisation
>>>     colibri_vf: Enable board specific USB initialisation for USB pen gpio
>>
>> Submitted these patches in single series, as few of the patches are
>> interdependent, thought it would be easy to keep them in same series.
>>
>> Shall we split this patchset as per the custodian maintainers to pick?
>>
>> Patchset 1: Add GPIO driver support for Freescale Vybrid platform,
>> enable support for GPIO support on Toradex Colibri VF50, VF61 modules.
>>
>> Patchset 2: Add device tree support for Freescale Vybrid Platform,
>> Toradex Colibri VF50, VF61 modules.
>>
>> Patchset 3: Add DSPI support for Toradex Colibri VF50, VF61 modules.
>>
>> Patchset 4: Add weak function for board specific USB initialization
>> for Freescale Vybrid platform.
>
> Generally, if a maintainer acks a patch, the patch could then be applied
> into another tree if this makes sense and avoid to introduce breakage,
> maybe in both trees. You patchset is related to u-boot-imx with
> exception for the USB part, but Marek has already acked it. I will check
> you patches soon, but I think it is ok if the whole patchset flows into
> u-boot-imx.
>
Ping!

> Best regards,
> Stefano Babic
>

Best regards,
Bhuvan