Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Paulo Cavalcanti" <promac@gmail.com>,
	"Vedran Miletić" <rivanvx@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: idt blue jack patch
Date: Tue, 24 Feb 2009 10:30:30 +0800	[thread overview]
Message-ID: <20090224023030.GA7778@localhost> (raw)
In-Reply-To: <s5hy6vx86zt.wl%tiwai@suse.de>

On Mon, Feb 23, 2009 at 06:15:18PM +0200, Takashi Iwai wrote:
> At Mon, 23 Feb 2009 14:00:43 +0100,
> I wrote:
> > > > > - if reconfig while playing audio, it will trigger a panic:
> > > > 
> > > > Ah, that's bad.  I know this can be a problem (and thus is marked as
> > > > EXPERIMENTAL :)
> > > > 
> > > > We need some mutex and/or flag to disable the reconfig during the
> > > > critical operation.
> > > 
> > > It won't be a trivial work. The reset/rebuild is a long and complex process.
> > > For the moment I'd suggest to simply fail reconfig if there are active streams,
> > 
> > Yep, that's what I thought of, too.
> > 
> > > so as to let this useful feature go upstream ASAP.
> > 
> > I'll merge the branch soon later.
> 
> FYI, now the branch is merged to master.
> The dynamic pincfg feature is available on alsa-driver snapshot, too.
> 
> Also, I added the check of opened streams before doing clear/reconfig
> work so that the kernel panic won't happen so easily.

That's great, thank you!

Regards,
Fengguang

  reply	other threads:[~2009-02-24  2:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  9:13 idt blue jack patch Paulo Cavalcanti
2009-02-16 10:55 ` Takashi Iwai
2009-02-18  2:04   ` Paulo Cavalcanti
2009-02-18  6:50     ` Takashi Iwai
2009-02-18  9:04       ` Paulo Cavalcanti
2009-02-18  9:44         ` Vedran Miletić
2009-02-18 15:24           ` Takashi Iwai
2009-02-19  3:02             ` Wu Fengguang
2009-02-19  3:22               ` Tobin Davis
2009-02-19  9:37                 ` Takashi Iwai
2009-02-20  1:00                 ` Wu Fengguang
2009-02-20 10:15                   ` Paulo Cavalcanti
2009-02-20 11:20                     ` Wu Fengguang
2009-02-20 14:16                       ` Paulo Cavalcanti
2009-02-20 14:31                         ` Wu Fengguang
2009-02-20 16:07                           ` Paulo Cavalcanti
2009-02-21  1:05                             ` Wu Fengguang
2009-02-20 17:18                   ` Takashi Iwai
2009-02-21  1:42                     ` Wu Fengguang
2009-02-21 16:28                       ` Takashi Iwai
2009-02-23  8:54                         ` Takashi Iwai
2009-02-23  9:53                           ` Wu Fengguang
2009-02-23 10:21                             ` Takashi Iwai
2009-02-23 12:58                               ` Wu Fengguang
2009-02-23 13:00                                 ` Takashi Iwai
2009-02-23 16:15                                   ` Takashi Iwai
2009-02-24  2:30                                     ` Wu Fengguang [this message]
2009-02-21  1:55                     ` Wu Fengguang
2009-02-21  2:42                       ` Paulo Cavalcanti
2009-02-21  2:56                         ` Wu Fengguang
2009-02-21  3:12                           ` Paulo Cavalcanti
2009-02-21 16:28                       ` Takashi Iwai

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=20090224023030.GA7778@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=promac@gmail.com \
    --cc=rivanvx@gmail.com \
    --cc=tiwai@suse.de \
    /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