diff options
| author | Rafał Miłecki <rafal@milecki.pl> | 2022-05-10 15:12:59 +0200 |
|---|---|---|
| committer | Miquel Raynal <miquel.raynal@bootlin.com> | 2022-05-16 18:37:48 +0200 |
| commit | bcdf0315a61a29eb753a607d3a85a4032de72d94 (patch) | |
| tree | f021207fad662a6ff6ddc70fd9c9d6cb3b268fc5 /drivers/mtd/devices | |
| parent | mtd: cfi_cmdset_0002: Rename chip_ready variables (diff) | |
| download | linux-bcdf0315a61a29eb753a607d3a85a4032de72d94.tar.xz linux-bcdf0315a61a29eb753a607d3a85a4032de72d94.zip | |
mtd: call of_platform_populate() for MTD partitions
Until this change MTD subsystem supported handling partitions only with
MTD partitions parsers. That's a specific / limited API designed around
partitions.
Some MTD partitions may however require different handling. They may
contain specific data that needs to be parsed and somehow extracted. For
that purpose MTD subsystem should allow binding of standard platform
drivers.
An example can be U-Boot (sub)partition with environment variables.
There exist a "u-boot,env" DT binding for MTD (sub)partition that
requires an NVMEM driver.
Ref: 5db1c2dbc04c ("dt-bindings: nvmem: add U-Boot environment variables binding")
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220510131259.555-1-zajec5@gmail.com
Diffstat (limited to 'drivers/mtd/devices')
0 files changed, 0 insertions, 0 deletions