From: john.ogness@linutronix.de (John Ogness)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 4/5] mtd: mxc_nand fixups
Date: Wed, 23 Jun 2010 12:10:08 +0200 [thread overview]
Message-ID: <80lja6awlb.fsf@merkur.tec.linutronix.de> (raw)
In-Reply-To: <AANLkTinVaXjCneg-XpxB7YNlmGOwQFTnm5RUcetPdToI@mail.gmail.com> (Ivo Clarysse's message of "Wed, 23 Jun 2010 11:23:55 +0200")
On 2010-06-23, Ivo Clarysse <ivo.clarysse@gmail.com> wrote:
> But is it OK to use a regular (non-volatile) variable to communicate
> between interrupt context and the non-interrupt context ?
In this case, yes.
> My original patch for i.MX21 used completions instead:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-April/012694.html
Ah. It seems you've been through all this before. I wish I had noticed
that thread before. I will need to check more carefully in the future.
Yes, your original patch achieves the exact same thing. Whether we use
wait_event() with a flag or wait_completion() really is the same
thing. So I guess Sascha can decide what we should do there.
What I like about your original patch is that only the i.MX21 has the
cost of constantly enabling/disabling the irq line. It adds 5
cpu_is_mx21() blocks to the code, but will lead to less work for the CPU
on non-i.MX21 boards.
John Ogness
next prev parent reply other threads:[~2010-06-23 10:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 17:01 [PATCH 4/5] mtd: mxc_nand fixups John Ogness
2010-06-18 20:54 ` Sascha Hauer
2010-06-19 20:25 ` John Ogness
2010-06-20 9:09 ` Ivo Clarysse
2010-06-20 9:21 ` [PATCHv2 " John Ogness
2010-06-21 11:47 ` Ivo Clarysse
2010-06-22 15:54 ` [PATCHv3 " John Ogness
2010-06-23 7:34 ` Ivo Clarysse
2010-06-23 8:48 ` John Ogness
2010-06-23 9:23 ` Ivo Clarysse
2010-06-23 10:10 ` John Ogness [this message]
2010-06-24 7:27 ` Sascha Hauer
2010-06-24 10:16 ` John Ogness
2010-06-25 14:50 ` Ivo Clarysse
2010-06-26 9:17 ` John Ogness
2010-07-01 14:24 ` Ivo Clarysse
2010-06-25 14:46 ` Ivo Clarysse
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=80lja6awlb.fsf@merkur.tec.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-arm-kernel@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