Skip to main content

Browse the archive

https://github.com/torvalds/linux
02 December 2022, 17:28:11 UTC
Revision 53e1719f3da0f095b8db1461bd12dd79f3246b84 authored by Ondrej Zary on 20 August 2012, 19:50:13 UTC, committed by Takashi Iwai on 21 August 2012, 05:29:40 UTC 
ALSA: snd-als100: fix suspend/resume
 
snd_card_als100_probe() does not set pcm field in struct snd_sb.
As a result, PCM is not suspended and applications don't know that they need
to resume the playback.

Tested with Labway A381-F20 card (ALS120).

Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
1 parent 535b6c5
Raw File
Tip revision: 53e1719f3da0f095b8db1461bd12dd79f3246b84 authored by Ondrej Zary on 20 August 2012, 19:50:13 UTC
ALSA: snd-als100: fix suspend/resume
Tip revision: 53e1719
IRQ.txt 
What is an IRQ?

An IRQ is an interrupt request from a device.
Currently they can come in over a pin, or over a packet.
Several devices may be connected to the same pin thus
sharing an IRQ.

An IRQ number is a kernel identifier used to talk about a hardware
interrupt source.  Typically this is an index into the global irq_desc
array, but except for what linux/interrupt.h implements the details
are architecture specific.

An IRQ number is an enumeration of the possible interrupt sources on a
machine.  Typically what is enumerated is the number of input pins on
all of the interrupt controller in the system.  In the case of ISA
what is enumerated are the 16 input pins on the two i8259 interrupt
controllers.

Architectures can assign additional meaning to the IRQ numbers, and
are encouraged to in the case  where there is any manual configuration
of the hardware involved.  The ISA IRQs are a classic example of
assigning this kind of additional meaning.
back to top