Current way of using pinctrl-mvebu

Chris Packham judge.packham at
Mon Jul 3 03:00:36 CEST 2023

Answering my own question (I think)

On Mon, Jul 3, 2023 at 12:10 PM Chris Packham <judge.packham at> wrote:
> Hi,
> I'm looking to upstream support for a new board with the Marvell AC5X
> SoC and some NAND driver changes to support the SoC/board. I've got
> things working when chain loading vendor based u-boot -> upstream
> u-boot but when I boot directly the NAND controller reports
> "pxa3xx-nand nand-controller at 805b0000: Ready timeout!!!".
> I think this is because the multi purpose pins are not in NAND/DEV
> mode. When chainloading the vendor u-boot has already done this so the
> driver works.
> I notice that pinctrl-mvebu.c just expects a single fixed pin-func
> property the covers all the functions required. How is the probe for
> this supposed to be configured?

If I define the proper pinconf subnodes and associate them with the
device then the pinmux does get probed. I still need to define a
pin-func property otherwise
mvebu_pinctl_probe()/mvebu_pinctrl_set_state_all() will fail with

> Thanks,
> Chris

More information about the U-Boot mailing list