1. Oct 25, 2013
    • Anssi Hannula's avatar
      ALSA: hda - hdmi: Re-setup pin and infoframe on plug-in on all codecs · 7342017f
      Anssi Hannula authored
      
      
      hdmi_setup_audio_infoframe() does not set up pin and infoframe if there
      is no connected sink. If a sink is connected while audio playback is
      already in progress, the pin and infoframe will not be properly set up,
      causing no audio or wrongly mapped audio.
      
      On Intel Haswell codecs the hdmi_setup_audio_infoframe() is already
      called again from hdmi_present_sense() when an ELD appears because
      transcoder:port mapping may have changed.
      
      Make the call non-Haswell-specific so that audio will be properly set up
      if the playback was started before a sink was connected.
      
      Tested on non-Haswell Intel HDMI codec by plugging sink in during
      playback.
      
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      7342017f
    • Anssi Hannula's avatar
      ALSA: hda - hdmi: Disable ramp-up/down for non-PCM on AMD codecs · 84d69e79
      Anssi Hannula authored
      Recent AMD HDMI codecs (revision ID 3 and later, 0x100300 as reported by
      procfs codec#0) have a configurable ramp-up/down functionality.
      
      The documentation ( http://www.x.org/docs/AMD/AMD_HDA_verbs_v2.pdf
      
       )
      specifies that 180 ("180/256 =~ 0.7") is recommended for PCM and 0 for
      non-PCM.
      
      Apply the recommended values according to provided S/PDIF AES0 settings
      since ramp-up/down does not make sense for non-PCM.
      
      v2: adapted to hdmi_ops infrastructure
      
      * More note from Anssi:
      actually, re-reading mails reveals that Olivier didn't find the
      expected difference with this setting, except for "maybe slightly
      slower startup with AES0=6" (i.e. value 0, which is unexpected).
      
      So maybe
      a) it makes too unnoticiable a difference, or
      b) only affects certain hardware (card and/or sink), or
      c) ramp-up/down is only triggered with the MUTE bit of
         ATI_VERB_SET_MULTICHANNEL_xx which is also rev3+ specific,
         but is not presently used by the driver,
      or something else.
      
      So there's a significant chance setting ramp rate is useless for us ATM,
      but probably does not do actual harm either.
      
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Tested-by: Olivier Langlois <olivier@trillion01.com> # v1
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      84d69e79
    • Anssi Hannula's avatar
      ALSA: hda - hdmi: Add HBR bitstreaming support for ATI/AMD HDMI codecs · 461cf6b3
      Anssi Hannula authored
      ATI/AMD HDMI codecs do not include standard HDA HDMI HBR support (which
      is required for bitstreaming DTS-HD and Dolby TrueHD), instead they have
      custom verbs for checking and enabling it.
      
      Add support for the ATI/AMD HDMI HBR verbs.
      
      The specification is available at:
      http://www.x.org/docs/AMD/AMD_HDA_verbs_v2.pdf
      
      
      
      v2: adapted to hdmi_ops infrastructure
      
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Tested-by: Peter Frühberger <fritsch@xbmc.org> # v1
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      461cf6b3
    • Anssi Hannula's avatar
      ALSA: hda - hdmi: Add ELD emulation for ATI/AMD codecs · 89250f84
      Anssi Hannula authored
      ATI/AMD HDMI/DP codecs do not include standard HDA ELD (EDID-like data)
      support.
      
      In place of providing access to an ELD buffer, various vendor-specific
      verbs are provided to provide the relevant information. Revision ID 3
      and later (0x100300 as reported by procfs codec#X) have support for
      providing more information than the previous revisions (but only if
      supported by the display driver).
      
      Generate ELD from the information provided by the vendor-specific verbs
      on ATI/AMD codecs.
      
      The specification is available at:
      http://www.x.org/docs/AMD/AMD_HDA_verbs_v2.pdf
      
      
      
      v2: moved code to hda_eld.c and cleaned it up
      v3: adapted to hdmi_ops infrastructure
      
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Tested-by: Peter Frühberger <fritsch@xbmc.org> # v2
      Tested-by: Olivier Langlois <olivier@trillion01.com> # v2
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      89250f84
    • Anssi Hannula's avatar
      ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support · 5a613584
      Anssi Hannula authored
      ATI/AMD codecs do not support all the standard HDA HDMI/DP functions,
      instead various vendor-specific verbs are provided.
      
      This commit addresses these missing functions:
      - standard channel mapping support
      - standard infoframe configuration support
      
      ATI/AMD provides their own verbs that allow the following:
      - setting CA for infoframe
      - setting down-mix information for infoframe
      - channel pair remapping
      - individual channel remapping (revision ID 3+, 0x100300+)
      
      The documentation for the verbs has now been released by AMD:
      http://www.x.org/docs/AMD/AMD_HDA_verbs_v2.pdf
      
      
      
      Add support for the ATI/AMD specific verbs and use them instead of the
      generic methods on ATI/AMD codecs. This allows multi-channel PCM audio
      to work.
      
      Channel remapping is restricted to pairwise mapping on codecs with
      revision ID 2 (0x100200 as reported by procfs codec#X) or lower. This
      means cards up to Radeon HD7670 as far as I know. This will not affect
      standard multi-channel modes since these codecs support automatic
      FC-LFE swapping for HDMI.
      
      ATI/AMD codecs do not advertise all of their supported rates, formats
      and channel counts, therefore that information is forced accordingly so
      that all HDMI 1.x PCM parameters are marked as supported.
      
      Support for multiple ports is also added to patch_atihdmi so that
      0x1002aa01 codecs with multiple ports will work properly when switched
      back to that patch.
      
      v2: splitted ELD emulation to a separate patch, tlv fixes
      v3: adapted to the new hdmi_ops infrastructure, fixed rev3+ vendor id
      
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Tested-by: Peter Frühberger <fritsch@xbmc.org> # v2
      Tested-by: Olivier Langlois <olivier@trillion01.com> # v2+rev3fix
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      5a613584
    • Anssi Hannula's avatar
      ALSA: hda - hdmi: Allow HDA patches to customize more operations · 307229d2
      Anssi Hannula authored
      
      
      Upcoming AMD multichannel support requires many customized operations
      (channel mapping, ELD, HBR) but can otherwise share most of its code
      with the generic patch.
      
      Add a local struct hdmi_ops containing customizable HDMI-specific
      callbacks and move the current code to those callbacks. Functionality is
      unaltered.
      
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      307229d2
  2. Oct 24, 2013
  3. Oct 22, 2013
  4. Oct 21, 2013