summaryrefslogtreecommitdiff
path: root/fs/jffs2
diff options
context:
space:
mode:
authorBrian Norris <computersforpeace@gmail.com>2016-01-05 10:39:45 -0800
committerBrian Norris <computersforpeace@gmail.com>2016-01-06 14:52:41 -0800
commitf7a8e38f07a17be90758559fe66fe7337096053f (patch)
tree56c3eb53ab4ca8bc90fe36a8f765e823154fb1c5 /fs/jffs2
parente576330033936d94a00068760a5744e27ce51a32 (diff)
mtd: nand: assign reasonable default name for NAND drivers
Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent device structure in sysfs") attempt to rely on the core MTD code to set the MTD name based on the parent device. However, nand_base tries to set a different default name according to the flash name (e.g., extracted from the ONFI parameter page), which means NAND drivers will never make use of the MTD defaults. This is not the intention of commit 853f1c58c4b2. This results in problems when trying to use the cmdline partition parser, since the MTD name is different than expected. Let's fix this by providing a default NAND name, where possible. Note that this is not really a great default name in the long run, since this means that if there are multiple MTDs attached to the same controller device, they will have the same name. But that is an existing issue and requires future work on a better controller vs. flash chip abstraction to fix properly. Fixes: 853f1c58c4b2 ("mtd: nand: omap2: show parent device structure in sysfs") Reported-by: Heiko Schocher <hs@denx.de> Signed-off-by: Brian Norris <computersforpeace@gmail.com> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com> Tested-by: Heiko Schocher <hs@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Frans Klaver <fransklaver@gmail.com> Cc: <stable@vger.kernel.org>
Diffstat (limited to 'fs/jffs2')
0 files changed, 0 insertions, 0 deletions