[PATCH v2 4/8] MTD: xway: remove endless loop
Hauke Mehrtens
hauke at hauke-m.de
Sun Jun 19 05:32:56 PDT 2016
On 06/19/2016 02:14 PM, Boris Brezillon wrote:
> On Sat, 18 Jun 2016 21:14:08 +0200
> Hauke Mehrtens <hauke at hauke-m.de> wrote:
>
>> From: John Crispin <john at phrozen.org>
>>
>> The reset loop logic could run into a endless loop. Lets fix it as
>> requested.
>> http://lists.infradead.org/pipermail/linux-mtd/2012-September/044240.html
>>
>> Signed-off-by: John Crispin <john at phrozen.org>
>> Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de>
>> ---
>> drivers/mtd/nand/xway_nand.c | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/mtd/nand/xway_nand.c b/drivers/mtd/nand/xway_nand.c
>> index 346781a..61176c4 100644
>> --- a/drivers/mtd/nand/xway_nand.c
>> +++ b/drivers/mtd/nand/xway_nand.c
>> @@ -73,16 +73,22 @@ struct xway_nand_data {
>> static void xway_reset_chip(struct nand_chip *chip)
>> {
>> unsigned long nandaddr = (unsigned long) chip->IO_ADDR_W;
>> + unsigned long timeout;
>> unsigned long flags;
>>
>> nandaddr &= ~NAND_WRITE_ADDR;
>> nandaddr |= NAND_WRITE_CMD;
>>
>> /* finish with a reset */
>> + timeout = jiffies + msecs_to_jiffies(20);
>> +
>> spin_lock_irqsave(&ebu_lock, flags);
>> writeb(NAND_WRITE_CMD_RESET, (void __iomem *) nandaddr);
>> - while ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
>> - ;
>> + do {
>> + if ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
>> + break;
>> + cond_resched();
>> + } while (!time_after_eq(jiffies, timeout));
>> spin_unlock_irqrestore(&ebu_lock, flags);
>> }
>>
>
> AFAICS, this function is doing exactly what
> ->cmdfunc(NAND_CMD_RESET, -1 , -1) does, except for the NAND_WAIT_WR_C
> test? What is this bit representing?
>
> I'd really prefer if you kill this function and just call ->cmdfunc()
> instead.
>
NAND_WAIT_WR_C indicates that the previous operation is finished.
When this is not needed I can call the generic function.
Hauke
More information about the linux-mtd
mailing list