From: Artem Bityutskiy <dedekind1@gmail.com>
To: Roland Stigge <stigge@antcom.de>
Cc: Huang Shijie <b32955@freescale.com>,
Bastian Hecht <hechtb@googlemail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Lei Wen <leiwen@marvell.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
dwmw2@infradead.org, kevin.wells@nxp.com, srinivas.bakki@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MTD: LPC32xx SLC NAND driver
Date: Tue, 15 May 2012 16:31:43 +0300 [thread overview]
Message-ID: <1337088703.2528.208.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FB25837.2050603@antcom.de>
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
On Tue, 2012-05-15 at 15:20 +0200, Roland Stigge wrote:
> >> while ((readl(...))&& timeout--> 0)
> >> cpu_relax();
>
> 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.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-15 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 13:29 [PATCH] MTD: LPC32xx SLC NAND driver Roland Stigge
2012-05-15 7:55 ` Artem Bityutskiy
2012-05-15 8:15 ` Huang Shijie
2012-05-15 13:20 ` Roland Stigge
2012-05-15 13:31 ` Artem Bityutskiy [this message]
2012-05-15 13:48 ` Roland Stigge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1337088703.2528.208.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=b32955@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=hechtb@googlemail.com \
--cc=kevin.wells@nxp.com \
--cc=lars@metafoo.de \
--cc=leiwen@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).