[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4FB25EAC.10205@antcom.de>
Date: Tue, 15 May 2012 15:48:28 +0200
From: Roland Stigge <stigge@...com.de>
To: dedekind1@...il.com
CC: Huang Shijie <b32955@...escale.com>,
Bastian Hecht <hechtb@...glemail.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Lei Wen <leiwen@...vell.com>, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
devicetree-discuss@...ts.ozlabs.org, dwmw2@...radead.org,
kevin.wells@....com, srinivas.bakki@....com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] MTD: LPC32xx SLC NAND driver
On 05/15/2012 03:31 PM, Artem Bityutskiy wrote:
>> As I understand loops_per_jiffy, this loop will take much longer
>> than the 100 ms you defined above?
>
> Not sure about much, but longer. The idea is that this is about
> the error path so if we report -EIO with a slight delay - no
> problem.
Turned out that the condition (FIFO empty) is always true for me.
Keeping the check for safety reasons for now, doing the timeout with
msleep()s which should be (cpu-wise) "social" enough and are
unexpected anyway but do approximate the ms timeout more precisely.
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists