aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/DocBook
diff options
context:
space:
mode:
authorAntonio Ospite <ao2@amarulasolutions.com>2013-01-29 06:56:28 -0500
committerTakashi Iwai <tiwai@suse.de>2013-01-29 09:10:35 -0500
commitd4dab5ab5bd0445420aa090185409bf3ae6ccd37 (patch)
tree1ce99aa3319fa0962989317e26862134dea7c72e /Documentation/DocBook
parent04044b819b21826f11f32e11aba54def635d8457 (diff)
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>
Diffstat (limited to 'Documentation/DocBook')
-rw-r--r--Documentation/DocBook/writing-an-alsa-driver.tmpl4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/DocBook/writing-an-alsa-driver.tmpl b/Documentation/DocBook/writing-an-alsa-driver.tmpl
index da2f443ab8ec..c0781bb1f9b5 100644
--- a/Documentation/DocBook/writing-an-alsa-driver.tmpl
+++ b/Documentation/DocBook/writing-an-alsa-driver.tmpl
@@ -2897,7 +2897,7 @@ struct _snd_pcm_runtime {
2897 2897
2898 <para> 2898 <para>
2899 When the pcm supports the pause operation (given in the info 2899 When the pcm supports the pause operation (given in the info
2900 field of the hardware table), the <constant>PAUSE_PUSE</constant> 2900 field of the hardware table), the <constant>PAUSE_PUSH</constant>
2901 and <constant>PAUSE_RELEASE</constant> commands must be 2901 and <constant>PAUSE_RELEASE</constant> commands must be
2902 handled here, too. The former is the command to pause the pcm, 2902 handled here, too. The former is the command to pause the pcm,
2903 and the latter to restart the pcm again. 2903 and the latter to restart the pcm again.
@@ -3084,7 +3084,7 @@ struct _snd_pcm_runtime {
3084 <section id="pcm-interface-interrupt-handler-timer"> 3084 <section id="pcm-interface-interrupt-handler-timer">
3085 <title>High frequency timer interrupts</title> 3085 <title>High frequency timer interrupts</title>
3086 <para> 3086 <para>
3087 This happense when the hardware doesn't generate interrupts 3087 This happens when the hardware doesn't generate interrupts
3088 at the period boundary but issues timer interrupts at a fixed 3088 at the period boundary but issues timer interrupts at a fixed
3089 timer rate (e.g. es1968 or ymfpci drivers). 3089 timer rate (e.g. es1968 or ymfpci drivers).
3090 In this case, you need to check the current hardware 3090 In this case, you need to check the current hardware