linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andy Walls <awalls@radix.net>
Cc: Tejun Heo <tj@kernel.org>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: workqueues tree build failure
Date: Thu, 26 Nov 2009 12:56:59 +0000	[thread overview]
Message-ID: <20091126125659.GD1037@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1259239225.3062.16.camel@palomino.walls.org>

On Thu, Nov 26, 2009 at 07:40:25AM -0500, Andy Walls wrote:

> I'm not sure doing things like I2C transactions in the in the top half
> of the IRQ handler is generally viable.  On shared IRQ lines, wouldn't
> this hold off the interrupt for another device for too long?

You're going to need to do I2C I/O to acknowledge and deassert the
interrupt on most of these devices so if someone's shared the IRQ line
with something that's too latency sensitive the hardware is broken
anyway.

> Workhandlers for deferring work are a nice way to avoid such bad system
> level interactions.

In order to cope with the fact that the IRQ can't be deasserted without
talking to the device it will almost always be masked while waiting for
the deferred work.

  reply	other threads:[~2009-11-26 12:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26  8:00 linux-next: workqueues tree build failure Stephen Rothwell
2009-11-26  8:04 ` Tejun Heo
2009-11-26  8:16   ` Peter Ujfalusi
2009-11-26  9:12     ` Tejun Heo
2009-11-26  9:24       ` Takashi Iwai
2009-11-26  9:31       ` Peter Ujfalusi
2009-11-26 10:18         ` Mark Brown
2009-11-26 11:44           ` Peter Ujfalusi
2009-11-26 12:49             ` Andy Walls
2009-11-26 13:23               ` Peter Ujfalusi
2009-11-26 12:40       ` Andy Walls
2009-11-26 12:56         ` Mark Brown [this message]
2009-11-27  2:02         ` Tejun Heo
2009-11-27  8:37           ` Takashi Iwai
2009-11-27  8:42             ` Tejun Heo
2009-11-27 10:09               ` Peter Ujfalusi
2009-11-27 11:38                 ` Mark Brown
2009-11-27 13:50           ` Andy Walls

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=20091126125659.GD1037@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=awalls@radix.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peter.ujfalusi@nokia.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    --cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).