From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: soundwire fixes for v6.16
Date: Fri, 18 Jul 2025 12:37:40 +0530 [thread overview]
Message-ID: <aHnyvOQxBkGTGpXF@vaman> (raw)
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
Hello Linus,
Please pull couple of driver fixes for soundwire subsystem for v6.16
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-6.16-fixes
for you to fetch changes up to 834bce6a715ae9a9c4dce7892454a19adf22b013:
soundwire: Revert "soundwire: qcom: Add set_channel_map api support" (2025-07-15 18:16:27 +0530)
----------------------------------------------------------------
soundwire fixes for v6.16
This contains couple of amd driver fixes for handles alerts when link is
down and cmd status register clear up. Also revert of qualcomm driver
channel map support due to regression observed.
----------------------------------------------------------------
Amit Pundir (1):
soundwire: Revert "soundwire: qcom: Add set_channel_map api support"
Vijendar Mukunda (2):
soundwire: amd: fix for handling slave alerts after link is down
soundwire: amd: fix for clearing command status register
drivers/soundwire/amd_manager.c | 4 +++-
drivers/soundwire/qcom.c | 26 --------------------------
2 files changed, 3 insertions(+), 27 deletions(-)
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-07-18 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 7:07 Vinod Koul [this message]
2025-07-18 18:50 ` [GIT PULL]: soundwire fixes for v6.16 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aHnyvOQxBkGTGpXF@vaman \
--to=vkoul@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox