diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2020-07-17 10:46:18 +0900 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-07-20 11:37:47 -0600 |
| commit | 245ad6c4adb4af5290f22acaba57ed0dd109e1f4 (patch) | |
| tree | 5475331b294dca23256b9358d0efde83ed9d3440 /drivers/gpio/mvebu_gpio.c | |
| parent | 105da6251a16cfc5db1ef374b5a18ea8df6e8a4c (diff) | |
fdt_support: call mtdparts_init() after finding MTD node to fix up
Platform code can call fdt_fixup_mtdparts() in order to hand U-Boot's
MTD partitions over to the Linux device tree.
Currently, fdt_fixup_mtdparts() calls mtdparts_init() in its entry.
If no target MTD device is found, an error message like follows is
displayed:
Device nand0 not found!
This occurs when the same code (e.g. arch/arm/mach-uniphier/fdt-fixup.c)
is shared among several boards, but not all of them support an MTD device.
Parse the DT first, then call mtdparts_init() only when the target MTD
node is found.
Yet, you still need to call mtdparts_init() before device_find().
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/gpio/mvebu_gpio.c')
0 files changed, 0 insertions, 0 deletions