Commit 5bda9fa1 authored by Nicolas Kaiser's avatar Nicolas Kaiser Committed by Jaroslav Kysela
Browse files

[ALSA] Documentation/sound/alsa/DocBook: typos



Some typos in Documentation/sound/alsa/DocBook.

Signed-off-by: default avatarNicolas Kaiser <nikai@nikai.net>
Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
Signed-off-by: default avatarJaroslav Kysela <perex@suse.cz>
parent f7ba7fc6
Loading
Loading
Loading
Loading
+2 −2
Original line number Diff line number Diff line
@@ -36,7 +36,7 @@
  </bookinfo>

  <chapter><title>Management of Cards and Devices</title>
     <sect1><title>Card Managment</title>
     <sect1><title>Card Management</title>
!Esound/core/init.c
     </sect1>
     <sect1><title>Device Components</title>
@@ -59,7 +59,7 @@
     <sect1><title>PCM Format Helpers</title>
!Esound/core/pcm_misc.c
     </sect1>
     <sect1><title>PCM Memory Managment</title>
     <sect1><title>PCM Memory Management</title>
!Esound/core/pcm_memory.c
     </sect1>
  </chapter>
+7 −7
Original line number Diff line number Diff line
@@ -2126,7 +2126,7 @@
	accessible via <constant>substream-&gt;runtime</constant>.
	This runtime pointer holds the various information; it holds
	the copy of hw_params and sw_params configurations, the buffer
	pointers, mmap records, spinlocks, etc.  Almost everyhing you
	pointers, mmap records, spinlocks, etc.  Almost everything you
	need for controlling the PCM can be found there.
	</para>

@@ -2339,7 +2339,7 @@ struct _snd_pcm_runtime {

	<para>
	  When the PCM substreams can be synchronized (typically,
	synchorinized start/stop of a playback and a capture streams),
	synchronized start/stop of a playback and a capture streams),
	you can give <constant>SNDRV_PCM_INFO_SYNC_START</constant>,
	too.  In this case, you'll need to check the linked-list of
	PCM substreams in the trigger callback.  This will be
@@ -3244,7 +3244,7 @@ struct _snd_pcm_runtime {
        You can even define your own constraint rules.
        For example, let's suppose my_chip can manage a substream of 1 channel
        if and only if the format is S16_LE, otherwise it supports any format
        specified in the <structname>snd_pcm_hardware</structname> stucture (or in any
        specified in the <structname>snd_pcm_hardware</structname> structure (or in any
        other constraint_list). You can build a rule like this:

        <example>
@@ -3767,7 +3767,7 @@ struct _snd_pcm_runtime {
        <para>
	Like <structfield>get</structfield> callback,
	when the control has more than one elements,
	all elemehts must be evaluated in this callback, too.
	all elements must be evaluated in this callback, too.
        </para>
      </section>

@@ -5528,12 +5528,12 @@ struct _snd_pcm_runtime {
  #ifdef CONFIG_PM
  static int snd_my_suspend(struct pci_dev *pci, pm_message_t state)
  {
          .... /* do things for suspsend */
          .... /* do things for suspend */
          return 0;
  }
  static int snd_my_resume(struct pci_dev *pci)
  {
          .... /* do things for suspsend */
          .... /* do things for suspend */
          return 0;
  }
  #endif
@@ -6098,7 +6098,7 @@ struct _snd_pcm_runtime {
<!-- ****************************************************** -->
<!-- Acknowledgments  -->
<!-- ****************************************************** -->
  <chapter id="acknowledments">
  <chapter id="acknowledgments">
    <title>Acknowledgments</title>
    <para>
      I would like to thank Phil Kerr for his help for improvement and