From: Mark Brown <broonie@sirena.org.uk>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, lethal@linux-sh.org,
dmitry.torokhov@gmail.com, linux-sh@vger.kernel.org
Subject: Re: [PATCH] Touch screen driver for the SuperH MigoR board
Date: Wed, 26 Mar 2008 11:29:44 +0000 [thread overview]
Message-ID: <20080326112943.GA26346@sirena.org.uk> (raw)
In-Reply-To: <aec7e5c30803252103x1534e43dv3f31a3bc731fc9bf@mail.gmail.com>
On Wed, Mar 26, 2008 at 01:03:09PM +0900, Magnus Damm wrote:
> interrupt and handle everything from a different context. Apart from
> avoiding serious latency issues, doing things from interrupt context
> simply won't work since the i2c bus driver may be interrupt driven and
> may sleep while waiting for the serial bus data to be sent.
Given that having devices that generate interrupts that need to be
serviced over interrupt driven buses is a fairly common pattern it seems
like it would be worth adding some helper code - if nothing else, it
would help with the documentation.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
next prev parent reply other threads:[~2008-03-26 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 11:16 [PATCH] Touch screen driver for the SuperH MigoR board Magnus Damm
2008-03-21 22:55 ` Andrew Morton
2008-03-26 4:03 ` Magnus Damm
2008-03-26 11:29 ` Mark Brown [this message]
2008-03-28 9:51 ` [PATCH] Touch screen driver for the SuperH MigoR board V2 Magnus Damm
2008-04-02 6:08 ` Dmitry Torokhov
2008-04-04 8:21 ` Magnus Damm
2008-04-04 16:14 ` Dmitry Torokhov
2008-04-25 10:29 ` Magnus Damm
2008-04-27 5:07 ` Dmitry Torokhov
2008-05-07 12:14 ` Magnus Damm
2008-07-01 10:33 ` [PATCH] Touch screen driver for the SuperH MigoR board Nicholas Beck
2008-07-01 11:22 ` Magnus Damm
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=20080326112943.GA26346@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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