1. 11 12月, 2009 4 次提交
  2. 18 11月, 2009 8 次提交
  3. 30 10月, 2009 10 次提交
  4. 03 8月, 2009 1 次提交
  5. 23 7月, 2009 1 次提交
  6. 11 2月, 2009 4 次提交
  7. 18 12月, 2008 1 次提交
  8. 27 11月, 2008 1 次提交
    • T
      ALSA: hda - Modularize HD-audio driver · 1289e9e8
      Takashi Iwai 提交于
      Split the monolithc HD-audio driver into several pieces:
       - snd-hda-intel   HD-audio PCI controller driver; loaded via udev
       - snd-hda-codec   HD-audio codec bus driver
       - snd-hda-codec-* Specific HD-audio codec drivers
      
      When built as modules, snd-hda-codec (that is invoked by snd-hda-intel)
      looks up the codec vendor ID and loads the corresponding codec module
      automatically via request_module().
      
      When built in a kernel, each codec drivers are statically hooked up
      before probing the PCI.
      
      This patch adds appropriate EXPORT_SYMBOL_GPL()'s and the module
      information for each driver, and driver-linking codes between
      codec-bus and codec drivers.
      
      TODO:
        - Avoid EXPORT_SYMBOL*() when built-in kernel
        - Restore __devinit appropriately depending on the condition
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      1289e9e8
  9. 22 11月, 2008 3 次提交
  10. 21 11月, 2008 1 次提交
  11. 19 11月, 2008 5 次提交
  12. 18 11月, 2008 1 次提交
    • W
      ALSA: ELD proc interface for HDMI sinks · 5f1e71b1
      Wu Fengguang 提交于
      Create /proc/asound/card<card_no>/eld#<codec_no> to reflect the audio
      configurations and capabilities of the attached HDMI sink.
      
      Some notes:
      
      - Shall we show an empty file if the ELD content is not valid?
        Well it's not that simple. There could be partially populated ELD,
        and there may be malformed ELD provided by buggy drivers/monitors.
        So expose ELD as it is.
      
      - The ELD retrieval routines rely on the Intel HDA interface,
        others are/could be universal and independent ones.
      
      - How do we name the proc file?
        If there are going to be two HDMI pins per codec, then the current naming
        scheme (eld#<codec no>) will fail. Luckily the user space dependencies should
        be minimal, so it would be trivial to do the rename if that happens.
      
      - The ELD proc file content is designed to be easy for scripts and human reading.
        Its lines all have the pattern:
      	  <item_name>\t[\t]*<item_value>
        where <item_name> is a keyword in c language, while <item_value> could be any
        contents, including white spaces. <item_value> could also be a null value.
      Signed-off-by: NWu Fengguang <wfg@linux.intel.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      5f1e71b1