1. 11 Jun, 2015 2 commits
    • Takashi Iwai's avatar
      ALSA: hda - Re-add the lost fake mute support · a686ec4c
      Takashi Iwai authored
      Yet another regression by the transition to regmap cache; for better
      usability, we had the fake mute control using the zero amp value for
      Conexant codecs, and this was forgotten in the new hda core code.
      
      Since the bits 4-7 are unused for the amp registers (as we follow the
      syntax of AMP_GET verb), the bit 4 is now used to indicate the fake
      mute.  For setting this flag, snd_hda_codec_amp_update() becomes a
      function from a simple macro.  The bonus is that it gained a proper
      function description.
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      a686ec4c
    • Takashi Iwai's avatar
      ALSA: hda - Continue probing even if i915 binding fails · bf06848b
      Takashi Iwai authored
      Currently snd-hda-intel driver aborts the probing of Intel HD-audio
      controller with i915 power well management when binding with i915
      driver via hda_i915_init() fails.  This is no big problem for Haswell
      and Broadwell where the HD-audio controllers are dedicated to
      HDMI/DP, thus i915 link is mandatory.  However, Skylake, Baytrail and
      Braswell have only one controller and both HDMI/DP and analog codecs
      share the same bus.  Thus, even if HDMI/DP isn't usable, we should
      keep the controller working for other codecs.
      
      For fixing this, this patch simply allows continuing the probing even
      if hda_i915_init() call fails.  This may leave stale sound components
      for HDMI/DP devices that are unbound with graphics.  We could abort
      the probing selectively, but from the code simplicity POV, it's better
      to continue in all cases.
      Reported-by: default avatarLibin Yang <libin.yang@intel.com>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      bf06848b
  2. 10 Jun, 2015 1 commit
    • Takashi Iwai's avatar
      ALSA: hda - Don't actually write registers for caps overwrites · 98a226ed
      Takashi Iwai authored
      Along with the transition to regmap for managing the cached parameter
      reads, the caps overwrite was also moved to regmap cache.  The cache
      change itself works, but it still tries to write the non-existing verb
      (the HDA parameter is read-only) wrongly.  It's harmless in most
      cases, but some chips are picky and may result in the codec
      communication stall.
      
      This patch avoids it just by adding the missing flag check in
      reg_write ops.
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      98a226ed
  3. 09 Jun, 2015 1 commit
  4. 08 Jun, 2015 1 commit
  5. 03 Jun, 2015 2 commits
  6. 02 Jun, 2015 1 commit
  7. 31 May, 2015 1 commit
  8. 30 May, 2015 1 commit
  9. 29 May, 2015 3 commits
  10. 28 May, 2015 1 commit
  11. 27 May, 2015 3 commits
  12. 26 May, 2015 1 commit
  13. 24 May, 2015 2 commits
  14. 20 May, 2015 3 commits
  15. 19 May, 2015 2 commits
  16. 18 May, 2015 4 commits
  17. 12 May, 2015 6 commits
  18. 11 May, 2015 1 commit
  19. 10 May, 2015 4 commits
    • Linus Torvalds's avatar
      Linux 4.1-rc3 · 030bbdbf
      Linus Torvalds authored
      030bbdbf
    • Linus Torvalds's avatar
      Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux · 01d07351
      Linus Torvalds authored
      Pull drm fixes from Dave Airlie:
       "I really need to get back to sending these on my Friday, instead of my
        Monday morning, but nothing too amazing in here: a few amdkfd fixes, a
        few radeon fixes, i915 fixes, one tegra fix and one core fix"
      
      * 'drm-fixes' of git://people.freedesktop.org/~airlied/linux:
        drm: Zero out invalid vblank timestamp in drm_update_vblank_count.
        drm/tegra: Don't use vblank_disable_immediate on incapable driver.
        drm/radeon: stop trying to suspend UVD sessions
        drm/radeon: more strictly validate the UVD codec
        drm/radeon: make UVD handle checking more strict
        drm/radeon: make VCE handle check more strict
        drm/radeon: fix userptr lockup
        drm/radeon: fix userptr BO unpin bug v3
        drm/amdkfd: Initialize sdma vm when creating sdma queue
        drm/amdkfd: Don't report local memory size
        drm/amdkfd: allow unregister process with queues
        drm/i915: Drop PIPE-A quirk for 945GSE HP Mini
        drm/i915: Sink rate read should be saved in deca-kHz
        drm/i915/dp: there is no audio on port A
        drm/i915: Add missing MacBook Pro models with dual channel LVDS
        drm/i915: Assume dual channel LVDS if pixel clock necessitates it
        drm/radeon: don't setup audio on asics that don't support it
        drm/radeon: disable semaphores for UVD V1 (v2)
      01d07351
    • Dave Airlie's avatar
      Merge tag 'drm-intel-fixes-2015-05-08' of git://anongit.freedesktop.org/drm-intel into drm-fixes · 332545b3
      Dave Airlie authored
      misc i915 fixes.
      
      * tag 'drm-intel-fixes-2015-05-08' of git://anongit.freedesktop.org/drm-intel:
        drm/i915: Drop PIPE-A quirk for 945GSE HP Mini
        drm/i915: Sink rate read should be saved in deca-kHz
        drm/i915/dp: there is no audio on port A
        drm/i915: Add missing MacBook Pro models with dual channel LVDS
        drm/i915: Assume dual channel LVDS if pixel clock necessitates it
      332545b3
    • Mario Kleiner's avatar
      drm: Zero out invalid vblank timestamp in drm_update_vblank_count. · fdb68e09
      Mario Kleiner authored
      Since commit 844b03f2 we make
      sure that after vblank irq off, we return the last valid
      (vblank count, vblank timestamp) pair to clients, e.g., during
      modesets, which is good.
      
      An overlooked side effect of that commit for kms drivers without
      support for precise vblank timestamping is that at vblank irq
      enable, when we update the vblank counter from the hw counter, we
      can't update the corresponding vblank timestamp, so now we have a
      totally mismatched timestamp for the new count to confuse clients.
      
      Restore old client visible behaviour from before Linux 3.17, but
      zero out the timestamp at vblank counter update (instead of disable
      as in original implementation) if we can't generate a meaningful
      timestamp immediately for the new vblank counter. This will fix
      this regression, so callers know they need to retry again later
      if they need a valid timestamp, but at the same time preserves
      the improvements made in the commit mentioned above.
      Signed-off-by: default avatarMario Kleiner <mario.kleiner.de@gmail.com>
      Cc: <stable@vger.kernel.org> #v3.17+
      
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Daniel Vetter <daniel@ffwll.ch>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      fdb68e09