diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2020-07-17 04:46:18 +0300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-07-25 23:46:57 +0300 |
| commit | 53a896649ac002bd569a6c2007498eb979075abf (patch) | |
| tree | 0b2101e3a10ef1c1510d3717ebe71e309419664c /drivers/mmc/xenon_sdhci.c | |
| parent | 331caeafad40dd457dbc669c05a9e0d8ebc7095f (diff) | |
| download | u-boot-53a896649ac002bd569a6c2007498eb979075abf.tar.xz | |
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/mmc/xenon_sdhci.c')
0 files changed, 0 insertions, 0 deletions