From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: ext Tejun Heo <tj@kernel.org>, Takashi Iwai <tiwai@suse.de>,
Andy Walls <awalls@radix.net>,
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>
Subject: Re: linux-next: workqueues tree build failure
Date: Fri, 27 Nov 2009 11:38:08 +0000 [thread overview]
Message-ID: <20091127113808.GC29821@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200911271209.18979.peter.ujfalusi@nokia.com>
On Fri, Nov 27, 2009 at 12:09:18PM +0200, Peter Ujfalusi wrote:
> For the record: on OMAP platforms the I2C implementation is sleeping during the
> transfer (internally using interrupt based transfer), which might be not that
> wise in the tasklet. Since the I2C bus is kind of a slow bus, this could take
> several ms in some cases.
There's also the possibility of contention with other users of the I2C
bus which doesn't help matters here.
next prev parent reply other threads:[~2009-11-27 11:38 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
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 [this message]
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=20091127113808.GC29821@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.