From: Ondrej Zary <linux@rainbow-software.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: als4000: enable burst mode
Date: Wed, 4 Aug 2010 21:56:44 +0200 [thread overview]
Message-ID: <201008042156.46344.linux@rainbow-software.org> (raw)
In-Reply-To: <s5hy6cm2mzv.wl%tiwai@suse.de>
On Wednesday 04 August 2010 21:31:32 Takashi Iwai wrote:
> At Wed, 4 Aug 2010 21:08:14 +0200,
>
> Ondrej Zary wrote:
> > On Wednesday 04 August 2010 07:43:44 Takashi Iwai wrote:
> > > At Tue, 3 Aug 2010 23:57:05 +0200,
> > >
> > > Ondrej Zary wrote:
> > > > Enable burst mode to prevent dropouts during high PCI bus usage.
> > > > The card is useless in X without this because of dropouts when
> > > > anything moves on the screen (at least with PCI VGA card). Enabling
> > > > this is also recommended by the datasheet (page 48).
> > > >
> > > > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
> > >
> > > Applied now. Thanks.
> >
> > My previous patch assumed that the DMA mode (represented by 3 lowest bits
> > of ALS4K_GCR99_DMA_EMULATION_CTRL register) is set to the default value
> > 0. If that's not the case, it might result in invalid mode to be set.
> > This v2 patch fixes this potential problem.
> >
> > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
>
> As the previous patch was already applied, could you give the
> incremental change?
Of course, sorry for that.
My previous patch assumed that the DMA mode (represented by 3 lowest bits of
ALS4K_GCR99_DMA_EMULATION_CTRL register) is set to the default value 0. If
that's not the case, it might result in invalid mode to be set.
This patch fixes this potential problem.
Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
--- linux-2.6.35-rc3-/sound/pci/als4000.c 2010-08-04 21:53:48.000000000 +0200
+++ linux-2.6.35-rc3/sound/pci/als4000.c 2010-08-04 20:57:00.000000000 +0200
@@ -765,7 +765,7 @@ static void snd_als4000_configure(struct
snd_als4k_gcr_write(chip, i, 0);
/* enable burst mode to prevent dropouts during high PCI bus usage */
snd_als4k_gcr_write(chip, ALS4K_GCR99_DMA_EMULATION_CTRL,
- snd_als4k_gcr_read(chip, ALS4K_GCR99_DMA_EMULATION_CTRL) | 0x04);
+ (snd_als4k_gcr_read(chip, ALS4K_GCR99_DMA_EMULATION_CTRL) & ~0x07) | 0x04);
spin_unlock_irq(&chip->reg_lock);
}
--
Ondrej Zary
next prev parent reply other threads:[~2010-08-04 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 21:57 als4000: enable burst mode Ondrej Zary
2010-08-04 5:43 ` Takashi Iwai
2010-08-04 19:08 ` Ondrej Zary
2010-08-04 19:31 ` Takashi Iwai
2010-08-04 19:56 ` Ondrej Zary [this message]
2010-08-04 21:20 ` 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=201008042156.46344.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=alsa-devel@alsa-project.org \
--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 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.