Re: [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active

At Tue, 08 Nov 2005 12:07:50 +0000,
R C wrote:
> 
> On Tue, 2005-11-08 at 12:36 +0100, Takashi Iwai wrote:
> [...]
> 
> >   Note that "goto done" may
> > require the lock again.  Also, the succeeding saa7134_dma_stop() is
> > superfluous.
> > 
> 
> No, it's not. dma_stop also affects the main saa7134 module, and it's
> needed there.

But saa7134_dma_stop() should be already called in trigger callback,
which is called via snd_pcm_stop().


Takashi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active
    • From: R C <[email protected]>

• References:
  • [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active
    • From: [email protected]
  • Re: [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active
    • From: Takashi Iwai <[email protected]>
  • Re: [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active
    • From: R C <[email protected]>

• Prev by Date: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad
• Next by Date: Re: [PATCH] i386: export genapic again
• Previous by thread: Re: [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active
• Next by thread: Re: [Patch 1/1] V4L (926) Saa7134 alsa can only be autoloaded after saa7134 is active
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]