From: Ryan Mallon <ryan@bluewatersys.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linus.walleij@stericsson.com, andre@bluewatersys.com,
linux-mtd@lists.infradead.org, akpm@linux-foundation.org,
avorontsov@ru.mvista.com, hartleys@visionengravers.com
Subject: Re: [patch 02/13] mtd: SST25L (non JEDEC) SPI Flash driver
Date: Mon, 21 Sep 2009 16:47:44 +1200 [thread overview]
Message-ID: <4AB70570.5050703@bluewatersys.com> (raw)
In-Reply-To: <1253380972.6317.22.camel@macbook.infradead.org>
David Woodhouse wrote:
> On Fri, 2009-09-18 at 12:51 -0700, akpm@linux-foundation.org wrote:
>> +static int sst25l_wait_till_ready(struct sst25l_flash *flash)
>> +{
>> + unsigned long deadline;
>> + int status, err;
>> +
>> + deadline = jiffies + MAX_READY_WAIT_JIFFIES;
>> + do {
>> + err = sst25l_status(flash, &status);
>> + if (err)
>> + return err;
>> + if (!(status & SST25L_STATUS_BUSY))
>> + return 0;
>> +
>> + cond_resched();
>> + } while (!time_after_eq(jiffies, deadline));
>> +
>> + return -ETIMEDOUT;
>> +}
>
> If your system is busy and you end up relinquishing the CPU for a long
> period of time during that cond_resched(), you could hit the timeout
> condition even though the hardware _is_ actually reporting 'ready'
> status by the time you get back on the CPU.
>
> It's unlikely, admittedly, but it's good practice to make sure it can't
> happen like that. Something like
>
> while (busy) {
> if (timed_out) return -ETIMEDOUT;
> cond_resched();
> }
>
Just thinking about this a bit more. We don't want to call cond_resched
if the device is ready immediately, and we want to do the check _after_
cond_resched each time through the loop. There are probably enough
places that this sort of thing gets used that it may be worth having a
generic function like this (untested):
int cond_resched_wait_timeout(unsigned long timeout_jiffies,
int (*cond_check)(void *cookie),
void *data)
{
unsigned long deadline;
int ret;
ret = cond_check(data);
if (ret == 1)
return 0;
if (ret < 0)
return ret;
deadline = jiffies + timeout_jiffies;
while (1) {
cond_resched();
ret = cond_check(data);
if (ret == 1)
return 0;
if (ret < 0)
return ret;
if (time_after_eq(jiffies, deadline))
return -ETIMEDOUT;
}
/* Not reached */
return 0;
}
Not sure if the name is entirely appropriate, or where it should go as a
generic function. Thoughts?
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon Unit 5, Amuri Park
Phone: +64 3 3779127 404 Barbadoes St
Fax: +64 3 3779135 PO Box 13 889
Email: ryan@bluewatersys.com Christchurch, 8013
Web: http://www.bluewatersys.com New Zealand
Freecall Australia 1800 148 751 USA 1800 261 2934
next prev parent reply other threads:[~2009-09-21 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 19:51 [patch 02/13] mtd: SST25L (non JEDEC) SPI Flash driver akpm
2009-09-19 17:22 ` David Woodhouse
2009-09-21 3:24 ` Ryan Mallon
2009-09-21 6:08 ` David Woodhouse
2009-09-21 4:47 ` Ryan Mallon [this message]
2009-09-21 6:14 ` David Woodhouse
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=4AB70570.5050703@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=akpm@linux-foundation.org \
--cc=andre@bluewatersys.com \
--cc=avorontsov@ru.mvista.com \
--cc=dwmw2@infradead.org \
--cc=hartleys@visionengravers.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-mtd@lists.infradead.org \
/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