Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 30 6月, 2011 1 次提交
  3. 29 6月, 2011 1 次提交
    • W
      ALSA: HDMI - fix ELD monitor name length · f5b2d0ef
      由 Wu Fengguang 提交于 
      I noticed that the last character of the ELD monitor name is lost,
this fixes the issue.

This fix should be confirming to the HDA spec, and works together with
the DRM part of the ELD patch.

The HDA spec does not mention that Monitor_Name_String is an '\0'
ending string, and it allows NML to be 1, which is only valid when MNL
does not count the possible ending '\0'.
Signed-off-by: NWu Fengguang <fengguang.wu@intel.com>
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      f5b2d0ef
  5. 28 6月, 2011 2 次提交
  7. 24 6月, 2011 1 次提交
  9. 23 6月, 2011 1 次提交
  11. 21 6月, 2011 4 次提交
  13. 20 6月, 2011 1 次提交
  15. 17 6月, 2011 1 次提交
  17. 15 6月, 2011 1 次提交
  19. 14 6月, 2011 1 次提交
  21. 13 6月, 2011 6 次提交
  23. 10 6月, 2011 3 次提交
  25. 07 6月, 2011 1 次提交
  27. 03 6月, 2011 4 次提交
  29. 28 5月, 2011 1 次提交
    • L
      ALSA: fix hda AZX_DCAPS_NO_TCSEL quirk check in driver_caps · 46f2cc80
      由 Linus Torvalds 提交于 
      Commit 9477c58e ("ALSA: hda - Reorganize controller quriks with bit
flags") changed the driver type compares into various quirk bits.
However, the check for AZX_DCAPS_NO_TCSEL got reverted: instead of
clearing TCSEL for chipsets that have that standard capability, it
cleared then when the NO_TCSEL bit was set.

This can lead to noise and repeated sounds - a weird "echo" behavior.
As the comment just above says: "Ensuring these bits are 0 clears
playback static on some HD Audio codecs".  Which is definitely true at
least on my Core i5 Westmere system.

Cc: Takashi Iwai <tiwai@suse.de>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      46f2cc80
  31. 26 5月, 2011 3 次提交
  33. 25 5月, 2011 3 次提交
    • T
      ALSA: hda - Use model=auto for Lenovo G555 · af4ccf4f
      由 Takashi Iwai 提交于 
      The new auto-parser fixes problems on Lenovo G555.
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      af4ccf4f
    • S
      ALSA: HDA: Unify HDMI hotplug handling. · 5d44f927
      由 Stephen Warren 提交于 
      This change unifies the initial handling of a pin's state with the code to
update a pin's state after a hotplug (unsolicited response) event. The
initial probing, and all updates, are now routed through hdmi_present_sense.

The stored PD and ELDV status is now always derived from GetPinSense verb
execution, and not from the data in the unsolicited response. This means:

a) The WAR for NVIDIA codec's UR.PD values ("old_pin_detect") can be
   removed, since this only affected the no-longer-used unsolicited
   response payload.

b) In turn, this means that most NVIDIA codecs can simply use
   patch_generic_hdmi instead of having a custom variant just to set
   old_pin_detect.

c) When PD && ELDV becomes true, no extra verbs are executed, because the
   GetPinSense that was previously executed by snd_hdmi_get_eld (really,
   hdmi_eld_valid) has simply moved into hdmi_present_sense.

d) When PD && ELDV becomes false, there is a single extra GetPinSense verb
   executed for codecs where old_pin_detect wasn't set, i.e. some NVIDIA,
   and all ATI/AMD and Intel codecs. I doubt this will be a performance
   issue.

The new unified code in hdmi_present_sense also ensures that eld->eld_valid
is not set unless eld->monitor_present is also set. This protects against
potential invalid combinations of PD and ELDV received from HW, and
transitively from a graphics driver.

Also, print the derived PD/ELDV bits from hdmi_present_sense so the kernel
log always displays the actual state stored, which will differ from the
values in the unsolicited response for NVIDIA HW where old_pin_detect was
previously set.

Finally, a couple of small tweaks originally by Takashi:

* Clear the ELD content to zero before reading it, so that if it's not
  read (i.e. when !(PD && ELDV)) it's in a known state.

* Don't show ELD fields in /proc ELD files when the ELD isn't valid.

The only possibility I can see for regression here is a codec where the
GetPinSense verb returns incorrect data. However, we're already exposed
to that, since that data is used (a) from hdmi_add_pin to set up the
initial pin state, and (b) within snd_hda_input_jack_report to query
a pin's presence value. As such, I don't believe any HW has bugs here.
Includes-changes-by: NTakashi Iwai <tiwai@suse.de>
Signed-off-by: NStephen Warren <swarren@nvidia.com>
Acked-by: NWu Fengguang <fengguang.wu@intel.com>
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      5d44f927
    • T
      ALSA: hda - Force AD1988_6STACK_DIG for Asus M3N-HT Deluxe · 4e60b4f8
      由 Tony Vroon 提交于 
      The microphone input on the back panel (pink connector)
stopped operating correctly after an upgrade from
2.6.35 to 2.6.38; the actual problem manifests itself
as a lack of microphone bias voltage (VREF_HIZ) on
node 0x17.
With AD1988_6STACK_DIG the maximum bias voltage (VREF_80)
is applied and the headset operates correctly.
Signed-off-by: NTony Vroon <tony@linx.net>
Tested-by: NDoug Redlich <pbrigade@nxltech.net>
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      4e60b4f8
  35. 24 5月, 2011 3 次提交
  37. 23 5月, 2011 1 次提交
  39. 20 5月, 2011 1 次提交