From 26b06940a9bd894c1a21d76b160a3daea0843417 Mon Sep 17 00:00:00 2001 From: Luka Perkov Date: Sun, 29 Jun 2014 23:29:57 +0000 Subject: mvebu: drop 3.10 support Signed-off-by: Luka Perkov SVN-Revision: 41406 --- ...a3xx-Use-waitfunc-to-wait-for-the-device-.patch | 34 ---------------------- 1 file changed, 34 deletions(-) delete mode 100644 target/linux/mvebu/patches-3.10/0141-mtd-nand-pxa3xx-Use-waitfunc-to-wait-for-the-device-.patch (limited to 'target/linux/mvebu/patches-3.10/0141-mtd-nand-pxa3xx-Use-waitfunc-to-wait-for-the-device-.patch') diff --git a/target/linux/mvebu/patches-3.10/0141-mtd-nand-pxa3xx-Use-waitfunc-to-wait-for-the-device-.patch b/target/linux/mvebu/patches-3.10/0141-mtd-nand-pxa3xx-Use-waitfunc-to-wait-for-the-device-.patch deleted file mode 100644 index 13fdffe..0000000 --- a/target/linux/mvebu/patches-3.10/0141-mtd-nand-pxa3xx-Use-waitfunc-to-wait-for-the-device-.patch +++ /dev/null @@ -1,34 +0,0 @@ -From 2a1254f505ca4d376eae81768e4d5d890b578d13 Mon Sep 17 00:00:00 2001 -From: Ezequiel Garcia -Date: Thu, 14 Nov 2013 18:25:27 -0300 -Subject: [PATCH 141/203] mtd: nand: pxa3xx: Use waitfunc() to wait for the - device to be ready - -In pxa3xx_nand_sensing() instead of simply using info->is_ready -after issuing a command, the correct way of checking is to wait -for the device to be ready through the chip's waitfunc(). - -Signed-off-by: Ezequiel Garcia -Tested-by: Daniel Mack -Signed-off-by: Brian Norris ---- - drivers/mtd/nand/pxa3xx_nand.c | 7 ++++--- - 1 file changed, 4 insertions(+), 3 deletions(-) - ---- a/drivers/mtd/nand/pxa3xx_nand.c -+++ b/drivers/mtd/nand/pxa3xx_nand.c -@@ -1040,10 +1040,11 @@ static int pxa3xx_nand_sensing(struct px - return ret; - - chip->cmdfunc(mtd, NAND_CMD_RESET, 0, 0); -- if (!info->need_wait) -- return 0; -+ ret = chip->waitfunc(mtd, chip); -+ if (ret & NAND_STATUS_FAIL) -+ return -ENODEV; - -- return -ENODEV; -+ return 0; - } - - static int pxa3xx_nand_scan(struct mtd_info *mtd) -- cgit v1.1