ALSA: Documentation: fix some typos

s/PAUSE_PUSE/PAUSE_PUSH/
s/happense/happens/

Signed-off-by: Antonio Ospite <ao2@amarulasolutions.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
This commit is contained in:
Antonio Ospite 2013-01-29 12:56:28 +01:00 committed by Takashi Iwai
parent 04044b819b
commit d4dab5ab5b
1 changed files with 2 additions and 2 deletions

View File

@ -2897,7 +2897,7 @@ struct _snd_pcm_runtime {
<para> <para>
When the pcm supports the pause operation (given in the info When the pcm supports the pause operation (given in the info
field of the hardware table), the <constant>PAUSE_PUSE</constant> field of the hardware table), the <constant>PAUSE_PUSH</constant>
and <constant>PAUSE_RELEASE</constant> commands must be and <constant>PAUSE_RELEASE</constant> commands must be
handled here, too. The former is the command to pause the pcm, handled here, too. The former is the command to pause the pcm,
and the latter to restart the pcm again. and the latter to restart the pcm again.
@ -3084,7 +3084,7 @@ struct _snd_pcm_runtime {
<section id="pcm-interface-interrupt-handler-timer"> <section id="pcm-interface-interrupt-handler-timer">
<title>High frequency timer interrupts</title> <title>High frequency timer interrupts</title>
<para> <para>
This happense when the hardware doesn't generate interrupts This happens when the hardware doesn't generate interrupts
at the period boundary but issues timer interrupts at a fixed at the period boundary but issues timer interrupts at a fixed
timer rate (e.g. es1968 or ymfpci drivers). timer rate (e.g. es1968 or ymfpci drivers).
In this case, you need to check the current hardware In this case, you need to check the current hardware