From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Shawn Guo <shawn.guo@freescale.com>,
ashishj3 <ashish.jangam@kpitcummins.com>,
Dajun <dajun.chen@diasemi.com>,
sameo@openedhand.com, linaro-dev@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/11] MFD: DA9052 MFD core module v2
Date: Sat, 23 Jul 2011 11:43:34 +0100 [thread overview]
Message-ID: <20110723104333.GA13883@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201107231150.31055.arnd@arndb.de>
On Sat, Jul 23, 2011 at 11:50:30AM +0200, Arnd Bergmann wrote:
> Yes, that makes sense. There are also cases where a mutex should really
> be a spinlock (which is by definition not interruptible), or vice
> versa. I don't know if this is one of them.
We would be using spinlocks except the underlying buses sleep waiting
for the hardware to complete the transfer - the operations are quick
enough from a user perspective but at the very low level we want the CPU
to be able to go off and do other things while they're happening.
next prev parent reply other threads:[~2011-07-23 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 14:37 [PATCH 01/11] MFD: DA9052 MFD core module v2 ashishj3
2011-07-05 14:55 ` Arnd Bergmann
2011-07-11 6:57 ` Ashish Jangam
2011-07-11 7:03 ` Mark Brown
2011-07-12 18:32 ` Arnd Bergmann
2011-07-12 18:40 ` Ashish Jangam
2011-07-21 15:46 ` Shawn Guo
2011-07-21 15:47 ` Mark Brown
2011-07-21 20:40 ` Arnd Bergmann
2011-07-22 8:59 ` Mark Brown
2011-07-23 9:50 ` Arnd Bergmann
2011-07-23 10:43 ` Mark Brown [this message]
2011-07-21 16:07 ` Shawn Guo
2011-07-24 18:49 ` Mark Brown
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=20110723104333.GA13883@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=ashish.jangam@kpitcummins.com \
--cc=dajun.chen@diasemi.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@openedhand.com \
--cc=shawn.guo@freescale.com \
/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