mtd: spi-nor: Decouple SPI NOR's device_node from controller device
Subsystems (3)
PATCH v2 1/2 mtd: spi-nor: Decouple SPI NOR's device_node from controller device
The problem this patch is trying to address is such, that SPI NOR flash devices attached to a dedicated SPI NOR controller cannot read their properties from the associated struct device_node.
A couple of facts first:
1) Each SPI NOR flash has a struct spi_nor associated with it.
2) Each SPI NOR flash has certain device properties associated with it, for example the OF property 'm25p,fast-read' is a good pick. These properties are used by the SPI NOR core to select which opcodes are sent to such SPI NOR flash. These properties are coming from spi_nor .dev->of_node .
The problem is, that for SPI NOR controllers, the struct spi_nor .dev element points to the struct device of the SPI NOR controller, not the SPI NOR flash. Therefore, the associated dev->of_node also is the one of the controller and therefore the SPI NOR core code is trying to parse the SPI NOR controller's properties, not the properties of the SPI NOR flash.
Note: The m25p80 driver is not affected, because the controller and
the flash are the same device, so the associated device_node of the controller and the flash are the same.
This patch adjusts the SPI NOR core such that the device_node is not picked from spi_nor .dev directly, but from a new separate spi_nor .flash_node element. This let's the SPI NOR controller drivers set up a different spi_nor .flash_node element for each SPI NOR flash.
This patch also fixes the controller drivers to be compatible with this modification and correctly set the spi_nor .flash_node element.
This patch is inspired by 5844feeaa4154d1c46d3462c7a4653d22356d8b4
mtd: nand: add common DT init code
--- drivers/mtd/devices/m25p80.c | 1 + drivers/mtd/spi-nor/fsl-quadspi.c | 1 + drivers/mtd/spi-nor/nxp-spifi.c | 1 + drivers/mtd/spi-nor/spi-nor.c | 2 +- include/linux/mtd/spi-nor.h | 2 ++ 5 files changed, 6 insertions(+), 1 deletion(-)
V2: - Rename .dn to .flash_node
- Add missing change to spi-nor.c
- Fix build issue in m25p80, where there was one deref. too much
drivers/mtd/devices/m25p80.c +1 -0
@@ -202,6 +202,7 @@ static int m25p_probe(struct spi_device *spi) nor->dev = &spi->dev; nor->mtd = &flash->mtd; + nor->flash_node = spi->dev.of_node; nor->priv = flash;spi_set_drvdata (spi, flash);
drivers/mtd/spi-nor/fsl-quadspi.c +1 -0
@@ -1017,6 +1017,7 @@ static int fsl_qspi_probe(struct platform_device *pdev) nor->mtd = mtd; nor->dev = dev; + nor->flash_node = np; nor->priv = q; mtd->priv = nor;
drivers/mtd/spi-nor/nxp-spifi.c +1 -0
@@ -334,6 +334,7 @@ static int nxp_spifi_setup_flash(struct nxp_spifi *spifi, spifi->mtd.priv = &spifi->nor; spifi->nor.mtd = &spifi->mtd; spifi->nor.dev = spifi->dev; + spifi->nor.flash_node = np; spifi->nor.priv = spifi; spifi->nor.read = nxp_spifi_read; spifi->nor.write = nxp_spifi_write;
drivers/mtd/spi-nor/spi-nor.c +1 -1
@@ -1026,7 +1026,7 @@ int spi_nor_scan(struct spi_nor *nor, const char *name, enum read_mode mode)const struct flash_info *info =NULL ;struct device *dev = nor->dev;struct mtd_info *mtd = nor->mtd; -struct device_node *np = dev->of_node; +struct device_node *np = nor->flash_node;int ret;int i;
include/linux/mtd/spi-nor.h +2 -0
@@ -142,6 +142,7 @@ enum spi_nor_option_flags {* @mtd: point to a mtd_info structure * @lock: the lock for the read/write/erase/lock/unlock operations * @dev: point to a spi device, or a spi nor controller device. +* @flash_node: point to a device node describing this flash instance. * @page_size: the page size of the SPI NOR * @addr_width: number of address bytes * @erase_opcode: the opcode for erasing a sector
@@ -174,6 +175,7 @@ struct spi_nor {struct mtd_info *mtd;struct mutex lock;struct device *dev; +struct device_node *flash_node;u32 page_size;u8 addr_width;u8 erase_opcode;
Signature · 1 line
2.1.4
PATCH 2/2 mtd: nand: Rename nand_chip .dn to .flash_node
Use a more descriptive name for the device_node element in struct nand_chip . This name matches the element name used for device_node property of a flash in the spi-nor framework.
--- drivers/mtd/nand/brcmnand/brcmnand.c | 5 +++-- drivers/mtd/nand/nand_base.c | 4 ++-- include/linux/mtd/nand.h | 4 ++-- 3 files changed, 7 insertions(+), 6 deletions(-)
drivers/mtd/nand/brcmnand/brcmnand.c +3 -2
@@ -1792,7 +1792,8 @@ static int brcmnand_setup_dev(struct brcmnand_host *host)memset (cfg,0 ,sizeof (*cfg)); - ret =of_property_read_u32 (chip->dn,"brcm,nand-oob-sector-size" , + ret =of_property_read_u32 (chip->flash_node, +"brcm,nand-oob-sector-size" , &oob_sector);if (ret) {/* Use detected size */
@@ -1899,7 +1900,7 @@ static int brcmnand_init_cs(struct brcmnand_host *host) mtd = &host->mtd; chip = &host->chip; - chip->dn = dn; + chip->flash_node = dn; chip->priv = host; mtd->priv = chip; mtd->name = devm_kasprintf(&pdev->dev, GFP_KERNEL, "brcmnand.%d",
drivers/mtd/nand/nand_base.c +2 -2
@@ -3846,8 +3846,8 @@ int nand_scan_ident(struct mtd_info *mtd, int maxchips,struct nand_flash_dev *type;int ret; -if (chip->dn) { - ret =nand_dt_init (mtd, chip, chip->dn); +if (chip->flash_node) { + ret =nand_dt_init (mtd, chip, chip->flash_node);if (ret)return ret; }
include/linux/mtd/nand.h +2 -2
@@ -544,7 +544,7 @@ struct nand_buffers {* flash device * @IO_ADDR_W: [BOARDSPECIFIC] address to write the 8 I/O lines of the * flash device. -* @dn: [BOARDSPECIFIC] device node describing this instance +* @flash_node: [BOARDSPECIFIC] device node describing this instance * @read_byte: [REPLACEABLE] read one byte from the chip * @read_word: [REPLACEABLE] read one word from the chip * @write_byte: [REPLACEABLE] write a single byte to the chip on the
@@ -647,7 +647,7 @@ struct nand_chip {void __iomem *IO_ADDR_R ;void __iomem *IO_ADDR_W ; -struct device_node *dn; +struct device_node *flash_node;uint8_t (*read_byte)(struct mtd_info *mtd);u16 (*read_word)(struct mtd_info *mtd);
Signature · 1 line
2.1.4
Quoted 44 lines · Marek Vasut
The problem this patch is trying to address is such, that SPI NOR flash devices attached to a dedicated SPI NOR controller cannot read their properties from the associated struct
device_node.A couple of facts first:
1) Each SPI NOR flash has a structspi_norassociated with it.
2) Each SPI NOR flash has certain device properties associated with it, for example the OF property 'm25p,fast-read' is a good pick. These properties are used by the SPI NOR core to select which opcodes are sent to such SPI NOR flash. These properties are coming fromspi_nor.dev->of_node .The problem is, that for SPI NOR controllers, the struct
spi_nor.dev element points to the struct device of the SPI NOR controller, not the SPI NOR flash. Therefore, the associateddev->of_nodealso is the one of the controller and therefore the SPI NOR core code is trying to parse the SPI NOR controller's properties, not the properties of the SPI NOR flash.Note: The m25p80 driver is not affected, because the controller and
the flash are the same device, so the associateddevice_nodeof the controller and the flash are the same.This patch adjusts the SPI NOR core such that the
device_nodeis not picked fromspi_nor.dev directly, but from a new separatespi_nor.flash_node element. This let's the SPI NOR controller drivers set up a differentspi_nor.flash_node element for each SPI NOR flash.This patch also fixes the controller drivers to be compatible with this modification and correctly set the
spi_nor.flash_node element.This patch is inspired by
5844feeaa4154d1c46d3462c7a4653d22356d8b4
mtd: nand: add common DT init codeSigned-off-by Marek Vasut <[email protected]>Cc Brian Norris <[email protected]>--- drivers/mtd/devices/m25p80.c | 1 + drivers/mtd/spi-nor/fsl-quadspi.c | 1 + drivers/mtd/spi-nor/nxp-spifi.c | 1 + drivers/mtd/spi-nor/spi-nor.c | 2 +- include/linux/mtd/spi-nor.h | 2 ++ 5 files changed, 6 insertions(+), 1 deletion(-)
Quoted 3 lines
V2: - Rename .dn to .flash_node
- Add missing change tospi-nor.c
- Fix build issue in m25p80, where there was one deref. too much
Pushed both to l2-mtd.git/next