linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Tejun Heo <tj@kernel.org>
Cc: 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>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: linux-next: workqueues tree build failure
Date: Thu, 26 Nov 2009 10:16:58 +0200	[thread overview]
Message-ID: <200911261016.58810.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <4B0E3677.6000603@kernel.org>

Hello,

On Thursday 26 November 2009 10:04:07 ext Tejun Heo wrote:
> 11/26/2009 05:00 PM, Stephen Rothwell wrote:
> > Hi Tejun,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > sound/soc/codecs/tlv320dac33.c: In function 'dac33_i2c_probe':
> > sound/soc/codecs/tlv320dac33.c:1121: error: implicit declaration of
> > function 'create_rt_workqueue' sound/soc/codecs/tlv320dac33.c:1121:
> > warning: assignment makes pointer from integer without a cast
> >
> > Caused by commit 1b2d88bf4c63ed3a8c9033c358905d3463aa8bc2 ("stop_machine:
> > reimplement without using workqueue") (which removed create_rt_workqueue
> > ()) interacting with commit c8bf93f0fe8c5a509a29e30f3bac823fa0f6d96e
> > ("ASoC: Codec driver for Texas Instruments tlv320dac33 codec") from the
> > sound tree.
> >
> > I have no idea how to fix this, so I have used the workqueues tree from
> > next-20091125 until someone can suggest a solution.
> 
> Takashi, RT workqueue is going away.  Do you really need it?

What can be used instead of RT workqueue?
The tlv320dac33 needs RT workqueue because I need to send the I2C command with 
minimum delay to the codec. If this can not be done (the workqueue is delayed), 
and the codec does not receive the command in time, it will literally die.

What are the options to replace the RT workqueue?

> 
> Thanks.
> 

-- 
Péter

  reply	other threads:[~2009-11-26  8:16 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 [this message]
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
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=200911261016.58810.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).