mtd: nand: omap: Synchronize the access to the ECC engine

Linux-MTD Mailing List linux-mtd at lists.infradead.org
Mon Dec 15 19:59:06 PST 2014


Gitweb:     http://git.infradead.org/?p=mtd-2.6.git;a=commit;h=1dc338e856744b8ca62addd1e29cc25fe6aae14d
Commit:     1dc338e856744b8ca62addd1e29cc25fe6aae14d
Parent:     4414d3efe57df6168d1ea564d56557d76b5ad8c7
Author:     Rostislav Lisovy <lisovy at gmail.com>
AuthorDate: Wed Oct 29 11:10:59 2014 +0100
Committer:  Brian Norris <computersforpeace at gmail.com>
CommitDate: Wed Nov 5 13:01:22 2014 -0800

    mtd: nand: omap: Synchronize the access to the ECC engine
    
    The AM335x Technical Reference Manual (spruh73j.pdf) says
    "Because the ECC engine includes only one accumulation context,
    it can be allocated to only one chip-select at a time ... "
    (7.1.3.3.12.3). Since the commit 97a288ba2cfa ("ARM: omap2+:
    gpmc-nand: Use dynamic platform_device_alloc()") gpmc-nand
    driver supports multiple NAND flash devices connected to
    the single controller.
    Use global 'struct nand_hw_control' among multiple NAND
    instances to synchronize the access to the single ECC Engine.
    
    Tested with custom AM335x board using 2x NAND flash chips.
    
    Signed-off-by: Rostislav Lisovy <lisovy at merica.cz>
    Acked-by: Roger Quadros <rogerq at ti.com>
    Signed-off-by: Brian Norris <computersforpeace at gmail.com>
---
 drivers/mtd/nand/omap2.c | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index b0f89d8..1ec0a1d 100644
--- a/drivers/mtd/nand/omap2.c
+++ b/drivers/mtd/nand/omap2.c
@@ -144,8 +144,13 @@ static u_char bch8_vector[] = {0xf3, 0xdb, 0x14, 0x16, 0x8b, 0xd2, 0xbe, 0xcc,
 	0xac, 0x6b, 0xff, 0x99, 0x7b};
 static u_char bch4_vector[] = {0x00, 0x6b, 0x31, 0xdd, 0x41, 0xbc, 0x10};
 
+/* Shared among all NAND instances to synchronize access to the ECC Engine */
+static struct nand_hw_control omap_gpmc_controller = {
+	.lock = __SPIN_LOCK_UNLOCKED(omap_gpmc_controller.lock),
+	.wq = __WAIT_QUEUE_HEAD_INITIALIZER(omap_gpmc_controller.wq),
+};
+
 struct omap_nand_info {
-	struct nand_hw_control		controller;
 	struct omap_nand_platform_data	*pdata;
 	struct mtd_info			mtd;
 	struct nand_chip		nand;
@@ -1685,9 +1690,6 @@ static int omap_nand_probe(struct platform_device *pdev)
 
 	platform_set_drvdata(pdev, info);
 
-	spin_lock_init(&info->controller.lock);
-	init_waitqueue_head(&info->controller.wq);
-
 	info->pdev		= pdev;
 	info->gpmc_cs		= pdata->cs;
 	info->reg		= pdata->reg;
@@ -1707,7 +1709,7 @@ static int omap_nand_probe(struct platform_device *pdev)
 
 	info->phys_base = res->start;
 
-	nand_chip->controller = &info->controller;
+	nand_chip->controller = &omap_gpmc_controller;
 
 	nand_chip->IO_ADDR_W = nand_chip->IO_ADDR_R;
 	nand_chip->cmd_ctrl  = omap_hwcontrol;



More information about the linux-mtd-cvs mailing list