Merge branch 'for-next' into for-linus

!Esound/core/pcm.c

!Esound/core/pcm_lib.c

!Esound/core/pcm_native.c

!Iinclude/sound/pcm.h

     </sect1>

     <sect1><title>PCM Format Helpers</title>

!Esound/core/pcm_misc.c

     <sect1><title>PCM Memory Management</title>

!Esound/core/pcm_memory.c

     </sect1>

     <sect1><title>PCM DMA Engine API</title>

!Esound/core/pcm_dmaengine.c

!Iinclude/sound/dmaengine_pcm.h

     </sect1>

  </chapter>

  <chapter><title>Control/Mixer API</title>

     <sect1><title>General Control Interface</title>

!Esound/core/info.c

     </sect1>

  </chapter>

  <chapter><title>Compress Offload</title>

     <sect1><title>Compress Offload API</title>

!Esound/core/compress_offload.c

!Iinclude/uapi/sound/compress_offload.h

!Iinclude/uapi/sound/compress_params.h

!Iinclude/sound/compress_driver.h

     </sect1>

  </chapter>

  <chapter><title>ASoC</title>

     <sect1><title>ASoC Core API</title>

!Iinclude/sound/soc.h

!Esound/soc/soc-core.c

!Esound/soc/soc-cache.c

!Esound/soc/soc-devres.c

!Esound/soc/soc-io.c

!Esound/soc/soc-pcm.c

     </sect1>

     <sect1><title>ASoC DAPM API</title>

!Esound/soc/soc-dapm.c

     </sect1>

     <sect1><title>ASoC DMA Engine API</title>

!Esound/soc/soc-generic-dmaengine-pcm.c

     </sect1>

  </chapter>

  <chapter><title>Miscellaneous Functions</title>

     <sect1><title>Hardware-Dependent Devices API</title>

!Esound/core/hwdep.c

     </sect1>

     <sect1><title>Jack Abstraction Layer API</title>

!Iinclude/sound/jack.h

!Esound/core/jack.c

!Esound/soc/soc-jack.c

     </sect1>

     <sect1><title>ISA DMA Helpers</title>

!Esound/core/isadma.c

          </informalexample>

        </para>

        <para>

	  The above callback can be simplified with a helper function,

	  <function>snd_ctl_enum_info</function>.  The final code

	  looks like below.

	  (You can pass ARRAY_SIZE(texts) instead of 4 in the third

	   argument; it's a matter of taste.)

          <informalexample>

            <programlisting>

<![CDATA[

  static int snd_myctl_enum_info(struct snd_kcontrol *kcontrol,

                          struct snd_ctl_elem_info *uinfo)

  {

          static char *texts[4] = {

                  "First", "Second", "Third", "Fourth"

          };

          return snd_ctl_enum_info(uinfo, 1, 4, texts);

  }

]]>

            </programlisting>

          </informalexample>

        </para>

        <para>

	  Some common info callbacks are available for your convenience:

	<function>snd_ctl_boolean_mono_info()</function> and

  Example:

	interrupts-extended = <&intc1 5 1>, <&intc2 1 0>;

A device node may contain either "interrupts" or "interrupts-extended", but not

both. If both properties are present, then the operating system should log an

error and use only the data in "interrupts".

2) Interrupt controller nodes

-----------------------------

Open Firmware Recommended Practice: Interrupt Mapping

http://www.openfirmware.org/1275/practice/imap/imap0_9d.pdf

Additionally to the properties specified in the above standards a host bridge

driver implementation may support the following properties:

- linux,pci-domain:

   If present this property assigns a fixed PCI domain number to a host bridge,

   otherwise an unstable (across boots) unique number will be assigned.

   It is required to either not set this property at all or set it for all

   host bridges in the system, otherwise potentially conflicting domain numbers

   may be assigned to root buses behind different host bridges.  The domain

   number for each host bridge in the system must be unique.

common pinctrl bindings used by client devices, including the meaning of the

phrase "pin configuration node".

TZ1090-PDC's pin configuration nodes act as a container for an abitrary number

TZ1090-PDC's pin configuration nodes act as a container for an arbitrary number

of subnodes. Each of these subnodes represents some desired configuration for a

pin, a group, or a list of pins or groups. This configuration can include the

mux function to select on those pin(s)/group(s), and various pin configuration