regression: nand/spi flashes listed in reversed order after "ARM: dts: at91: Switch to the new NAND bindings"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



After this patch, which is of course much appreciated:

1004a2977bdc7566bca87c565541c3232ed467c4
Refs: v4.12-rc1-7-g1004a2977bdc
Author:     Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx>
AuthorDate: Tue May 30 11:20:53 2017 +0200
Commit:     Alexandre Belloni <alexandre.belloni@xxxxxxxxxxxxxxxxxx>
CommitDate: Wed May 31 11:55:41 2017 +0200

    ARM: dts: at91: Switch to the new NAND bindings

    Use the new EBI/NAND bindings to declare NAND chips and remove old NAND
    nodes along the way.

    Note that we keep using old bindings in at91rm9200.dtsi because this
    SoC is not supported by the EBI driver.

The listing and indexing of my mtd devices changed:

root@after:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00010000 "spi32766.0"
...
mtd4: 32000000 00080000 "rootfs"
mtd5: 0bc00000 00080000 "config"

root@before:~# cat /proc/mtd
dev:    size   erasesize  name
...
mtd3: 32000000 00080000 "rootfs"
mtd4: 0bc00000 00080000 "config"
mtd5: 00080000 00010000 "spi32766.0"


I assume sorting the mtd listing in a specific order is not supported
nor desired by the mtd maintainers. So I'm not argueing about that.

But since the index of rootfs device is hard-coded in the cmdline, the
fw-utils config file and a custom script to backup/retrieve
configuration, this is causing me some problems.

The nand is partitioned, the spi is not:
mtdparts=mtdparts=atmel_nand:2M(foo),2M(bar),32M(baz),800M(rootfs),-(config)

While the bootargs can be fixed easily by using the human readable
name (ubi.mtd=rootfs). I can't retrieve that human readable name from
udev alone, nor can I build something from major/minor alone, since
the major is the same for nand/spi flash.

root@before:/etc/udev/rules.d# udevadm info /dev/mtd3
P: /devices/platform/ahb/40000000.nand/mtd/mtd3
N: mtd3
E: DEVNAME=/dev/mtd3
E: DEVPATH=/devices/platform/ahb/40000000.nand/mtd/mtd3
E: DEVTYPE=mtd
E: MAJOR=90
E: MINOR=6

root@dSS:/etc/udev/rules.d# udevadm info /dev/mtd5
P: /devices/platform/ahb/ahb:apb/fffc8000.spi/spi_master/spi32766/spi32766.0/mtd/mtd5
N: mtd5
E: DEVNAME=/dev/mtd5
E: DEVPATH=/devices/platform/ahb/ahb:apb/fffc8000.spi/spi_master/spi32766/spi32766.0/mtd/mtd5
E: DEVTYPE=mtd
E: MAJOR=90
E: MINOR=10
E: OF_COMPATIBLE_0=st,m25p40
E: OF_COMPATIBLE_N=1
E: OF_FULLNAME=/ahb/apb/spi@fffc8000/m25p40@0
E: OF_NAME=m25p40
E: SUBSYSTEM=mtd

What is the preferred to make the rootfs agnostic of a particular mtd
listing order

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/



[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux