Skip to content
Snippets Groups Projects
  1. Nov 06, 2018
    • Takashi Iwai's avatar
      ALSA: hda - Fix incorrect clearance of thinkpad_acpi hooks · 5e93a125
      Takashi Iwai authored
      Since the commit c647f806 ("ALSA: hda - Allow multiple ADCs for
      mic mute LED controls") we allow enabling the mic mute LED with
      multiple ADCs.  The commit changed the function return value to be
      zero or a negative error, while this change was overlooked in the
      thinkpad_acpi helper code where it still expects a positive return
      value for success.  This eventually leads to a NULL dereference on a
      system that has only a mic mute LED.
      
      This patch corrects the return value check in the corresponding code
      as well.
      
      Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=201621
      
      
      Fixes: c647f806 ("ALSA: hda - Allow multiple ADCs for mic mute LED controls")
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      5e93a125
  2. Oct 30, 2018
    • Takashi Sakamoto's avatar
      ALSA: firewire-lib: fix insufficient PCM rule for period/buffer size · 826b5de9
      Takashi Sakamoto authored
      
      In a former commit, PCM constraint based on LCM of SYT_INTERVAL was
      obsoleted with PCM rule. However, the new PCM rule brings -EINVAL in
      some cases that max/min values of size of buffer/period is not
      multiples of one of values of SYT_INTERVAL. For example, pulseaudio
      always fail to configure PCM substream.
      
      This commit changes strategy for the PCM rule. Although the buggy rules
      had a single dependency (rate from period, period from rate, rate from
      buffer, buffer from rate), a revised rule has double dependencies
      (period from period/rate, buffer from buffer/rate). A step of value is
      calculated with table of SYT_INTERVAL and list of available rates. This
      prevents interval template which brings -EINVAL to a call of
      snd_interval_refine().
      
      Fixes: 59502295('ALSA: firewire-lib: add PCM rules to obsolete PCM constraints based on LCM of SYT_INTERVAL')
      Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      826b5de9
  3. Oct 29, 2018
    • Alex Stanoev's avatar
      ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops · ac237c28
      Alex Stanoev authored
      
      The Creative Audigy SE (SB0570) card currently exhibits an audible pop
      whenever playback is stopped or resumed, or during silent periods of an
      audio stream. Initialise the IZD bit to the 0 to eliminate these pops.
      
      The Infinite Zero Detection (IZD) feature on the DAC causes the output
      to be shunted to Vcap after 2048 samples of silence. This discharges the
      AC coupling capacitor through the output and causes the aforementioned
      pop/click noise.
      
      The behaviour of the IZD bit is described on page 15 of the WM8768GEDS
      datasheet: "With IZD=1, applying MUTE for 1024 consecutive input samples
      will cause all outputs to be connected directly to VCAP. This also
      happens if 2048 consecutive zero input samples are applied to all 6
      channels, and IZD=0. It will be removed as soon as any channel receives
      a non-zero input". I believe the second sentence might be referring to
      IZD=1 instead of IZD=0 given the observed behaviour of the card.
      
      This change should make the DAC initialisation consistent with
      Creative's Windows driver, as this popping persists when initialising
      the card in Linux and soft rebooting into Windows, but is not present on
      a cold boot to Windows.
      
      Signed-off-by: default avatarAlex Stanoev <alex@astanoev.com>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      ac237c28
  4. Oct 27, 2018
  5. Oct 23, 2018
  6. Oct 21, 2018
  7. Oct 19, 2018
  8. Oct 18, 2018
    • Philipp Klocke's avatar
      ALSA: i2c/cs8427: Fix int to char conversion · eb7ebfa3
      Philipp Klocke authored
      
      Compiling with clang yields the following warning:
      
      sound/i2c/cs8427.c:140:31: warning: implicit conversion from 'int'
      to 'char' changes value from 160 to -96 [-Wconstant-conversion]
          data[0] = CS8427_REG_AUTOINC | CS8427_REG_CORU_DATABUF;
                  ~ ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
      
      Because CS8427_REG_AUTOINC is defined as 128, it is too big for a
      char field.
      So change data from char to unsigned char, that it can hold the value.
      
      This patch does not change the generated code.
      
      Signed-off-by: default avatarPhilipp Klocke <philipp97kl@gmail.com>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      eb7ebfa3
  9. Oct 17, 2018
  10. Oct 16, 2018
  11. Oct 15, 2018
  12. Oct 14, 2018
  13. Oct 12, 2018
Loading