From: Takashi Iwai <tiwai@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] sound fixes for 6.0-rc8 or final
Date: Tue, 27 Sep 2022 10:30:00 +0200 [thread overview]
Message-ID: <87zgelfcdz.wl-tiwai@suse.de> (raw)
Linus,
please pull sound fixes for v6.0-rc8 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-6.0-rc8
The topmost commit is c35fbea48659ec99a4f532c9ee9e8692405afdd0
----------------------------------------------------------------
sound fixes for 6.0-rc8 or final
hopefully the last PR for 6.0: here we have a few device-specific
fixes, mostly for ASoC. All look small / trivial enough.
----------------------------------------------------------------
Martin Povišer (1):
ASoC: tas2770: Reinit regcache on reset
Oder Chiou (1):
ASoC: rt5640: Fix the issue of the abnormal JD2 status
Pierre-Louis Bossart (2):
ASoC: Intel: sof_sdw: add support for Dell SKU 0AFF
ALSA: hda: intel-dsp-config: add missing RaptorLake PCI IDs
SJLIN0 (1):
ASoC: nau8824: Fix semaphore is released unexpectedly
Shengjiu Wang (1):
ASoC: imx-card: Fix refcount issue with of_node_put
---
sound/hda/intel-dsp-config.c | 10 +++++++
sound/soc/codecs/nau8824.c | 17 +++++++++--
sound/soc/codecs/nau8824.h | 1 +
sound/soc/codecs/rt5640.c | 64 ++++++++++++++++++++++++++++------------
sound/soc/codecs/rt5640.h | 14 +++++++++
sound/soc/codecs/tas2770.c | 3 ++
sound/soc/fsl/imx-card.c | 4 +++
sound/soc/intel/boards/sof_sdw.c | 10 +++++++
8 files changed, 101 insertions(+), 22 deletions(-)
next reply other threads:[~2022-09-27 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 8:30 Takashi Iwai [this message]
2022-09-27 14:37 ` [GIT PULL] sound fixes for 6.0-rc8 or final 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=87zgelfcdz.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.