Message ID | 20240718054606.799665-1-avromanov@salutedevices.com |
---|---|
Headers | show |
Series | Introduce mtdblock device | expand |
Hi, > Tested only on SPI NAND, so bind is made only for > SPI NAND drivers. If tried to test this with the SPI NOR framework but I couldn't get it to work. The SPI NOR flash didn't register with/was found by the mtdblock subsystem. I guess that is probably because the SPI NOR flash has it's own UCLASS_SPI_FLASH. There is some kind of compatibility layer (drivers/mtd/spi/sf_mtd.c) but it doesn't register a UCLASS_MTD. Do you have any idea how to get this to work? -michael
Hi Michael, Sorry for the late reply. On Fri, Jul 19, 2024 at 08:57:04AM +0200, Michael Walle wrote: > Hi, > > > Tested only on SPI NAND, so bind is made only for > > SPI NAND drivers. > > If tried to test this with the SPI NOR framework but I couldn't get > it to work. The SPI NOR flash didn't register with/was found by the > mtdblock subsystem. I guess that is probably because the SPI NOR > flash has it's own UCLASS_SPI_FLASH. There is some kind of > compatibility layer (drivers/mtd/spi/sf_mtd.c) but it doesn't > register a UCLASS_MTD. > > Do you have any idea how to get this to work? I think you have to try bind driver via mtd_bind(), just like I do for SPI-NAND in patch "spinand: bind mtdblock". I see what in file drivers/mtd/spi/sf_probe.c there is struct mtd_info and also you have U_BOOT_DRIVER. Maybe try to bind there? > > -michael