1. 22 Jun, 2021 8 commits
  2. 21 Jun, 2021 14 commits
  3. 20 Jun, 2021 3 commits
    • Takashi Iwai's avatar
      ALSA: hda/realtek: Fix bass speaker DAC mapping for Asus UM431D · f8fbcdfb
      Takashi Iwai authored
      Asus Zenbook 14 UM431D has two speaker pins and a headphone pin, and
      the auto-parser ends up assigning the bass to the third DAC 0x06.
      Although the tone comes out, it's inconvenient because this DAC has no
      volume control unlike two other DACs.
      
      For obtaining the volume control for the bass speaker, this patch
      enforces the mapping to let both front and bass speaker pins sharing
      the same DAC.  It's not ideal but a little bit of improvement.
      
      Since we've already applied the same workaround for another ASUS
      machine, we just need to hook the chain to the existing quirk.
      
      BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=212547
      Cc: <stable@vger.kernel.org>
      Link: https://lore.kernel.org/r/20210620065952.18948-1-tiwai@suse.deSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      f8fbcdfb
    • Elia Devito's avatar
      ALSA: hda/realtek: Improve fixup for HP Spectre x360 15-df0xxx · 434591b2
      Elia Devito authored
      On HP Spectre x360 15-df0xxx, after system boot with plugged headset, the
      headset mic are not detected.
      Moving pincfg and DAC's config to single fixup function fix this.
      
      [ The actual bug in the original code was that it used a chain to
        ALC286_FIXUP_SPEAKER2_TO_DAC1, and it contains not only the DAC1
        route fix but also another chain to ALC269_FIXUP_THINKPAD_ACPI.
        I thought the latter one is harmless for non-Thinkpad, but it
        doesn't seem so; it contains again yet another chain to
        ALC269_FIXUP_SKI_IGNORE, and this might be bad for some machines,
        including this HP machine.  -- tiwai ]
      Signed-off-by: default avatarElia Devito <eliadevito@gmail.com>
      Cc: <stable@vger.kernel.org>
      Link: https://lore.kernel.org/r/20210619204105.5682-1-eliadevito@gmail.comSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      434591b2
    • Takashi Sakamoto's avatar
      ALSA: bebob: add support for ToneWeal FW66 · 50ebe562
      Takashi Sakamoto authored
      A user of FFADO project reported the issue of ToneWeal FW66. As a result,
      the device is identified as one of applications of BeBoB solution.
      
      I note that in the report the device returns contradictory result in plug
      discovery process for audio subunit. Fortunately ALSA BeBoB driver doesn't
      perform it thus it's likely to handle the device without issues.
      
      I receive no reaction to test request for this patch yet, however it would
      be worth to add support for it.
      
      daniel@gibbonmoon:/sys/bus/firewire/devices/fw1$ grep -r . *
      Binary file config_rom matches
      dev:244:1
      guid:0x0023270002000000
      hardware_version:0x000002
      is_local:0
      model:0x020002
      model_name:FW66
      power/runtime_active_time:0
      power/runtime_active_kids:0
      power/runtime_usage:0
      power/runtime_status:unsupported
      power/async:disabled
      power/runtime_suspended_time:0
      power/runtime_enabled:disabled
      power/control:auto
      subsystem/drivers_autoprobe:1
      uevent:MAJOR=244
      uevent:MINOR=1
      uevent:DEVNAME=fw1
      units:0x00a02d:0x010001
      vendor:0x002327
      vendor_name:ToneWeal
      fw1.0/uevent:MODALIAS=ieee1394:ven00002327mo00020002sp0000A02Dver00010001
      fw1.0/power/runtime_active_time:0
      fw1.0/power/runtime_active_kids:0
      fw1.0/power/runtime_usage:0
      fw1.0/power/runtime_status:unsupported
      fw1.0/power/async:disabled
      fw1.0/power/runtime_suspended_time:0
      fw1.0/power/runtime_enabled:disabled
      fw1.0/power/control:auto
      fw1.0/model:0x020002
      fw1.0/rom_index:15
      fw1.0/specifier_id:0x00a02d
      fw1.0/model_name:FW66
      fw1.0/version:0x010001
      fw1.0/modalias:ieee1394:ven00002327mo00020002sp0000A02Dver00010001
      
      Cc: Daniel Jozsef <daniel.jozsef@gmail.com>
      Reference: https://lore.kernel.org/alsa-devel/20200119164335.GA11974@workstation/Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20210619083922.16060-1-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      50ebe562
  4. 18 Jun, 2021 4 commits
  5. 17 Jun, 2021 6 commits
    • Zhen Lei's avatar
      ALSA: aoa: remove unnecessary oom message · 37d122c5
      Zhen Lei authored
      Fixes scripts/checkpatch.pl warning:
      WARNING: Possible unnecessary 'out of memory' message
      
      Remove it can help us save a bit of memory.
      Signed-off-by: default avatarZhen Lei <thunder.leizhen@huawei.com>
      Link: https://lore.kernel.org/r/20210617102746.1709-1-thunder.leizhen@huawei.comSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      37d122c5
    • Takashi Iwai's avatar
      ALSA: seq: oss: Fix error check at system port creation · c485f7e9
      Takashi Iwai authored
      The system port creation in ALSA OSS sequencer was wrongly checked
      against to the port number that can be never negative.  The error code
      should be checked rather against the ioctl call.
      
      This patch corrects the error check.
      Reported-by: default avatarDan Carpenter <dan.carpenter@oracle.com>
      Link: https://lore.kernel.org/r/20210617134742.6321-1-tiwai@suse.deSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      c485f7e9
    • Takashi Sakamoto's avatar
      ALSA: firewire-motu: fix stream format for MOTU 8pre FireWire · fc36ef80
      Takashi Sakamoto authored
      My previous refactoring for ALSA firewire-motu driver brought regression
      to handle MOTU 8pre FireWire. The packet format is not operated correctly.
      
      Cc: <stable@vger.kernel.org>
      Fixes: dfbaa4dc ("ALSA: firewire-motu: add model-specific table of chunk count")
      Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20210614083133.39753-1-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      fc36ef80
    • Daehwan Jung's avatar
      ALSA: usb-audio: fix rate on Ozone Z90 USB headset · aecc19ec
      Daehwan Jung authored
      It mislabels its 96 kHz altsetting and that's why it causes some noise
      Signed-off-by: default avatarDaehwan Jung <dh10.jung@samsung.com>
      Cc: <stable@vger.kernel.org>
      Link: https://lore.kernel.org/r/1623836097-61918-1-git-send-email-dh10.jung@samsung.comSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      aecc19ec
    • Takashi Sakamoto's avatar
      ALSA: firewire-motu: add support for MOTU 896 · b431f16f
      Takashi Sakamoto authored
      MOTU 896 is a second model in MOTU FireWire series, produced in 2001. This
      model consists of three chips:
      
       * Texas Instruments TSB41AB2 (Physical layer for IEEE 1394 bus)
       * Philips Semiconductors PDI 1394L21BE (Link layer for IEEE 1394 bus and
         packet processing layer)
       * QuickLogic QuickRAM QL4016 (Data block processing layer and digital
         signal processing)
      
      This commit adds a support for the model, with its unique protocol as
      version 1. The features of this protocol are:
      
       * no MIDI support.
       * Rx packets have no data chunks for control and status messages.
       * Tx packets have 2 bytes for control and status messages in the end of
         each data block.
       * The most of settings are represented in bit flag in one quadlet address
         (0x'ffff'f000'0b14).
       * It's selectable to use signal on optical interface, however the device
         has no register specific to it. The state has effect just to whether
         to exclude differed data chunks.
       * The internal multiplexer is not configured by software.
      
      Just after powering on, the device has a quirk to fail handling
      transaction. I recommend users to connect the device enough after powering
      on.
      
      $ python3 crpp < /sys/bus/firewire/devices/fw1/config_rom
                     ROM header and bus information block
                     -----------------------------------------------------------------
      400  04102814  bus_info_length 4, crc_length 16, crc 10260
      404  31333934  bus_name "1394"
      408  20001000  irmc 0, cmc 0, isc 1, bmc 0, cyc_clk_acc 0, max_rec 1 (4)
      40c  0001f200  company_id 0001f2     |
      410  0000d645  device_id 000000d645  | EUI-64 0001f2000000d645
      
                     root directory
                     -----------------------------------------------------------------
      414  0004c65c  directory_length 4, crc 50780
      418  030001f2  vendor
      41c  0c0083c0  node capabilities per IEEE 1394
      420  8d000006  --> eui-64 leaf at 438
      424  d1000001  --> unit directory at 428
      
                     unit directory at 428
                     -----------------------------------------------------------------
      428  0003ab34  directory_length 3, crc 43828
      42c  120001f2  specifier id
      430  13000002  version
      434  17102801  model
      
                     eui-64 leaf at 438
                     -----------------------------------------------------------------
      438  0002057d  leaf_length 2, crc 1405
      43c  0001f200  company_id 0001f2     |
      440  0000d645  device_id 000000d645  | EUI-64 0001f2000000d645
      Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20210616082847.124688-3-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      b431f16f
    • Takashi Sakamoto's avatar
      ALSA: firewire-motu: add support for MOTU 828 · d13d6b28
      Takashi Sakamoto authored
      MOTU 828 is a first model in MOTU FireWire series, produced in 2001. This
      model consists of three chips:
       * Texas Instruments TSB41AB1 (Physical layer for IEEE 1394 bus)
       * Philips Semiconductors 1394L21BE (Link layer for IEEE 1394 bus and
         packet processing layer)
       * QuickLogic QuickRAM QL4016 (Data block processing layer and digital
         signal processing)
      
      This commit adds a support for this model, with its unique protocol as
      version 1. The features of this protocol are:
      
       * no MIDI support.
       * Rx packets have no data chunks for control and status messages.
       * Tx packets have 2 data chunks for control and status messages in the
         end of each data block. The chunks consist of data block counter
         (4 byte) and message (2 byte).
       * All of settings are represented in bit flag in one quadlet address
         (0x'ffff'f000'0b00).
       * When optical interface is configured as S/PDIF, signals of the interface
         is multiplexed for packets, instead of signals of coaxial interface.
       * The internal multiplexer is not configured by software.
      
      I note that the device has a quirk to mute output voluntarily during
      receiving batch of packets in the beginning of packet streaming. The
      operation to unmute should be done by software enough after the device
      shifts the state, however it's not deterministic. Furthermore, just
      after switching rate of sampling clock, the device keeps the state longer.
      This patch manages to sleep 100 msec before unmute operation, but it may
      fail to release the mute in the case that the rate is changed. As a
      workaround, users can restart packet streaming at the same rate, or write
      to specific register from userspace.
      
      $ python3 crpp < /sys/bus/firewire/devices/fw1/config_rom
                     ROM header and bus information block
                     -----------------------------------------------------------------
      400  04105c54  bus_info_length 4, crc_length 16, crc 23636
      404  31333934  bus_name "1394"
      408  20001000  irmc 0, cmc 0, isc 1, bmc 0, cyc_clk_acc 0, max_rec 1 (4)
      40c  0001f200  company_id 0001f2     |
      410  00005015  device_id 0000005015  | EUI-64 0001f20000005015
      
                     root directory
                     -----------------------------------------------------------------
      414  0004c65c  directory_length 4, crc 50780
      418  030001f2  vendor
      41c  0c0083c0  node capabilities per IEEE 1394
      420  8d000006  --> eui-64 leaf at 438
      424  d1000001  --> unit directory at 428
      
                     unit directory at 428
                     -----------------------------------------------------------------
      428  00035052  directory_length 3, crc 20562
      42c  120001f2  specifier id
      430  13000001  version
      434  17101800  model
      
                     eui-64 leaf at 438
                     -----------------------------------------------------------------
      438  0002eeb6  leaf_length 2, crc 61110
      43c  0001f200  company_id 0001f2     |
      440  00005015  device_id 0000005015  | EUI-64 0001f20000005015
      Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20210616082847.124688-2-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      d13d6b28
  6. 16 Jun, 2021 2 commits
  7. 14 Jun, 2021 2 commits
  8. 12 Jun, 2021 1 commit