Linux sound subsystem maintainer Takashi Iwai of SUSE began the Linux 7.4 sound pull request by noting that “the AI flood continues” with there continuing to be a lot of new patches coming as a result of AI/LLM agents devising patches as well as uncovering new kernel bugs.

Takashi went on to explain that it was another busy cycle with changes in the sound subsystem from lots of core code hardening to new platforms and codecs as well. The core ALSA code has been hardened against some race conditions, there’s a buffer leak fix in the compression offload code, race fixes in the JACK code, and other race conditions and more typical C bug fixes. The OSS sequencer emulation code has also been marked as deprecated for Linux 7.4.

On the hardware side, the Linux 7.4 sound updates include support for compressed audio playback on SOF IPC4 with Intel Tigerlake and newer. There is also AMD ACP 7.0/7.F sound IP support with SoundWire and the PDM controller. The new AMD ACP 7.0/7.F IP appears for upcoming Ryzen Zen 6 platforms.

There are also quirks for many different Intel/AMD laptops from the likes of Lenovo, ASUS, HP, AAcer, HONOR, MSI, and others.

New codec drivers are for the ESS ES9039Q2M, Nuvoton NAU83G60 amplifier, Senary SN624x SoundWire SDCA codec.

Also new is the Qualcomm QAIF driver for their Shikra platform.

More details on the many sound changes for Linux 7.4 via this pull ( https://lore.kernel.org/lkml/[email protected]/ ).

  • @[email protected]
    16•1 day ago

    We’re blaming constructors for writing driver because they use AI ?

    Can’t wait for this anti-AI slop to stop.

    You read me right.

    • @[email protected]
      3•14 hours ago

      Coding is one of the few usecases for AI I don’t have issues with per say, but that is with the caveat that it is done by a competent coder who knows what they’re doing to make things work better more quickly and with fewer bugs and issues. AI shouldn’t replace peoples jobs, except for maybe CEOs, it should be an efficiency multiplier and free people up from doing a load of busy work. Unfortunately I see AI being used as an excuse to fire people and make tye world a worse place in the search for immediate gains for companies without thought of the long term consequences.

      • @[email protected]English
        1•47 minutes ago

        If coders where as good as they say they are online we wouldn’t have as many bugs in software as we do.

      • Mordikan
        5•18 hours ago

        What specifically is slop about the 7.4 sound changes?

        • @[email protected]
          5•15 hours ago

          I didn’t say 7.4 is slop. You spoke against people who are anti-slop, which generally suggests pro-slop.

          Can’t wait for this anti-AI slop to stop.

          • Mordikan
            3•15 hours ago

            I think this is the first one that’s actually pro slop.

            So, what is the “actually pro slop” part of original comment? It sounds like the poster just said something against hype culture (either pro or anti) and you jumped to default trash mode.

            What is the actual complaint (if any) that you have?

            • setVeryLoud(true);
              2•14 hours ago

              They’re talking about people who are “anti AI slop” which is a weird stance to take. Slop bad. LLMs are just tools, which can be misused, but slop always bad.

              • Mordikan
                2•2 hours ago

                What’s weird is it isn’t even about AI generated code, but the disclosure of it via tag. It’s kinda redundantly stupid given the same PR with or without the tag is still subject to the same review process.

                Slop code (AI or human generated) gets eliminated at that point. There is no practical reason for people to throw a tantrum over this. The argument I know someone will try to make is that there are too many AI PRs and they need a way to distinguish from them. The problem is that just means the review process is “What flair did you use?” which is not a process at all.