Passing NAND mtdparts to OMAP2+ Kernel

[Adam Ford]

I posted this on the linux-omap list, and I was asked to post this on
the linux-mtd list:


I tried to remove the MTD partitions from the Linux device tree, and I
noticed that there was no partition information being pushed anymore
unless I changed the mtdparts name in U-Boot.

It appears as if the MTD drivers have changed a bit.  I found a few
e-mails floating around that attempt to fix this

Commit f7a8e38f07a17be907585 ("mtd: nand: assign reasonable default
name for NAND drivers") attempts to address this, and someone over at
https://patchwork.ozlabs.org/patch/707065/ attempted to address it as
well in a slightly different way.

Both of them refer to the same commit: 853f1c58c4b2 ("mtd: nand:
omap2: show parent device structure in sysfs") as the source for the
issue.

It now appears as if the name "omap2-nand.0" was replaced with
"30000000.nand"  Is this intentional? It seems like a lot of people
will have to update their bootloaders if they want to pass 'mtdparts'
from the bootloader to the kernel.

I am not a member of the MTD mailing list, so maybe this is more
properly sent over there, but since it's an OMAP related thing, I
thought I'd post it here.  My other ARM boards don't appear to be
impacted.  If the trend is to not pass the partition info from U-boot,
I can live with that too.  I was just more curious to know what the
long term plan is and what solution is recommended.

I have verified this in 4.11-RC4 and 4.9.18

adam