[U-Boot] [PATCH v1 13/19] arm64: mvebu_armada_37xx: Use Armada 37xx pinctrl driver by default

Stefan Roese sr at denx.de
Thu Mar 29 10:02:15 UTC 2018


Hi Marek,

(Ken, please keep the list always on Cc)

On 27.03.2018 04:12, Ken Ma wrote:
> Thanks a lot for your greak work on a37xx bug fixes.
> 
> For your patch of “arm64: mvebu_armada_37xx: Use Armada 37xx pinctrl 
> driver by default 
> <https://www.mail-archive.com/search?l=u-boot@lists.denx.de&q=subject:%22%5C%5BU%5C-Boot%5C%5D+%5C%5BPATCH+v1+13%5C%2F19%5C%5D+arm64%5C%3A+mvebu_armada_37xx%5C%3A+Use+Armada+37xx%09pinctrl+driver+by+default%22&o=newest>”, 
> I do the work in the blow 3 patches:
> 
> https://patchwork.ozlabs.org/patch/890818/ “Revert "arm64: a37xx: dts: 
> Add pin control nodes to DT"”
> 
> https://patchwork.ozlabs.org/patch/890805/ “arm64: a37xx: remove old 
> pinctrl implementation”,
> 
> In this patch I keep the function of board_early_init_f() as “return 0” 
> directly in order to add EEPROM initialization and system information 
> initialization in the future.
> 
> https://patchwork.ozlabs.org/patch/890802/ "arm64: a37xx: defconfig: 
> Enable PINCTRL and GPIO support for ESPRESSOBin board"
> 
>           In this patch, I add CONFIG_CMD_GPIO, CONFIG_DM_GPIO, 
> CONFIG_PINCTRL and CONFIG_PINCTRL_ARMADA_37XX to a37xx espressobin board 
> config file since Stenfan has enabled GPIO/pinctrl for a37xx DB board in 
> “arm64: mvebu_db-88f3720_defconfig: Enable PINCTRL and GPIO support”.
> 
>           And CONFIG_PINCTRL, CONFIG_PINCTRL_GENERIC and CONFIG_PINMUX 
> are enabled by default, so in my option CONFIG_PINCTRL_ARMADA_37XX is 
> enough.

Marek, how should we continue with the current A37xx patches on the
list. Are you okay with me pulling the patches from Ken / Marvell first
and you generating patches on top of these?

Additionally, it would help me, if you could send your phy related
patches as a separate patchset as well. Would this be possible?

Thanks,
Stefan


More information about the U-Boot mailing list