Commit d4dab5ab authored by Antonio Ospite's avatar Antonio Ospite Committed by Takashi Iwai

ALSA: Documentation: fix some typos

s/PAUSE_PUSE/PAUSE_PUSH/
s/happense/happens/
Signed-off-by: default avatarAntonio Ospite <ao2@amarulasolutions.com>
Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
parent 04044b81
...@@ -2897,7 +2897,7 @@ struct _snd_pcm_runtime { ...@@ -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 { ...@@ -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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment