1. 26 1月, 2012 1 次提交
  2. 25 1月, 2012 1 次提交
  3. 20 1月, 2012 1 次提交
  4. 19 1月, 2012 3 次提交
  5. 08 1月, 2012 1 次提交
  6. 12 12月, 2011 1 次提交
  7. 08 12月, 2011 3 次提交
    • T
      ALSA: hda/realtek - Fix lost speaker volume controls · 0a34b42b
      Takashi Iwai 提交于
      When there are the same or more number of HP pins are available, HP pins
      are used as the primary outputs instead of the speaker pins.  But, in
      some cases (especially with ALC663 & co), some DACs are available only
      with a later pin and it's assigned to a speaker, and since the driver
      parses the pins from the lower NID, such a DAC was skipped eventually
      without assignments.  This resulted in a regression, the missing speaker
      volume control in the new parser.
      
      As a workaround for this, now the driver retries the pin->DAC mapping
      again after restoring the speaker-pins as primary.  This is still an ad
      hoc fix, but it works so far for most of Realtek codecs.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      0a34b42b
    • T
      ALSA: hda/realtek - Create "Bass Speaker" for two speaker pins · fbabc246
      Takashi Iwai 提交于
      On systems with two speaker pins, the secondary speaker pin is mostly
      assigned to a bass speaker instead of a surround.  Thus it makes more
      sense to rename the control properly.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      fbabc246
    • T
      ALSA: hda/realtek - Don't create extra controls with channel suffix · 766ddee6
      Takashi Iwai 提交于
      The multiple headphone or speaker pins are usually provided to
      output the same stream unlike line-out jacks (which are supposed
      to be multi-channel surrounds).  Thus giving a mixer name like
      "Headphone Surround" is rather confusing.  Instead, when multiple
      headphone volumes are available, use index with the same "Headphone"
      name.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      766ddee6
  8. 02 12月, 2011 2 次提交
  9. 23 11月, 2011 2 次提交
  10. 16 11月, 2011 4 次提交
    • T
      ALSA: hda - Merge input-jack helpers to hda_jack.c · aad37dbd
      Takashi Iwai 提交于
      We can use the very same table in hda_jack.c for managing the list for
      input-jack elements, too.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      aad37dbd
    • T
      ALSA: hda - Manage unsol tags in hda_jack.c · 3a93897e
      Takashi Iwai 提交于
      Manage the tags assigned for unsolicited events dynamically together
      with the jack-detection routines.  Basically this is almost same as what
      we've done in patch_sigmatel.c.  Assign the new tag number for each new
      unsol event, associate with the given NID and the action type, etc.
      
      With this change, now all pins looked over in snd_hda_jack_add_kctls()
      are actually enabled for detection now even if the pins aren't used for
      jack-retasking by the driver.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      3a93897e
    • T
      ALSA: hda - Create jack-detection kcontrols · 01a61e12
      Takashi Iwai 提交于
      Create kcontrols for pin jack-detections, which work similarly like
      jack-input layer.  Each control will notify when the jack is plugged or
      unplugged, and also user can read the value at any time via the normal
      control API.
      
      The control elements are created with iface=CARD, so that they won't
      appear in the mixer apps.
      
      So far, only the pins that enabled the jack-detection are registered.
      For covering all pins, the transition of the common unsol-tag handling
      would be needed.  Stay tuned.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      01a61e12
    • T
      ALSA: hda - Cache the jack-detection value · 1835a0f9
      Takashi Iwai 提交于
      Introduce a table containing the pins and their jack-detection states
      for avoiding the unnecessary verbs to check the pin status at each time.
      
      When the unsol event is enabled via snd_hda_jack_detect_enable(), it
      automatically adds the given NID to the table.  Then the driver supposes
      that the codec driver will set the dirty flag appropariately when an
      unsolicited event is invoked for that pin.
      
      The behavior for reading other pins that aren't registered in the table
      doesn't change.  Only the pins assigned to the table are cached, so far.
      
      In near futre, this table can be extended to use the central place for
      the unsolicited events of all pins, etc, and eventually include the
      jack-detect kcontrols that replace the current input-jack stuff.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      1835a0f9
  11. 15 11月, 2011 4 次提交
  12. 14 11月, 2011 1 次提交
  13. 10 11月, 2011 7 次提交
  14. 09 11月, 2011 3 次提交
  15. 08 11月, 2011 6 次提交