From: Cezary Rojewski <cezary.rojewski@intel.com>
To: broonie@kernel.org
Cc: tiwai@suse.com, perex@perex.cz,
amadeuszx.slawinski@linux.intel.com, linux-sound@vger.kernel.org,
Cezary Rojewski <cezary.rojewski@intel.com>
Subject: [PATCH 0/3] ASoC: Intel: avs: Add rt5640 board support
Date: Fri, 30 May 2025 16:21:17 +0200 [thread overview]
Message-ID: <20250530142120.2944095-1-cezary.rojewski@intel.com> (raw)
Small set of patches intoducing two low-impact improvements to rt5640
codec driver and then avs_rt5640 machine board driver. The board
behavior is based on existing boards such as avs_rt274.
In regard to the retry-device-verification change, there is number of
similar "fixes" found in the Realtek code in sound/soc/codecs. What I
provide here is verified with tests, the delay is not mentioned in the
spec I have access to.
Cezary Rojewski (2):
ASoC: codecs: rt5640: Drop dummy register names
ASoC: Intel: avs: Add rt5640 machine board
Xinxin Wan (1):
ASoC: codecs: rt5640: Retry DEVICE_ID verification
sound/soc/codecs/rt5640.c | 43 ++--
sound/soc/codecs/rt5640.h | 6 +-
sound/soc/intel/avs/board_selection.c | 27 +++
sound/soc/intel/avs/boards/Kconfig | 12 ++
sound/soc/intel/avs/boards/Makefile | 2 +
sound/soc/intel/avs/boards/rt5640.c | 270 ++++++++++++++++++++++++++
6 files changed, 338 insertions(+), 22 deletions(-)
create mode 100644 sound/soc/intel/avs/boards/rt5640.c
--
2.25.1
next reply other threads:[~2025-05-30 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 14:21 Cezary Rojewski [this message]
2025-05-30 14:21 ` [PATCH 1/3] ASoC: codecs: rt5640: Drop dummy register names Cezary Rojewski
2025-05-30 14:21 ` [PATCH 2/3] ASoC: codecs: rt5640: Retry DEVICE_ID verification Cezary Rojewski
2025-05-30 14:21 ` [PATCH 3/3] ASoC: Intel: avs: Add rt5640 machine board Cezary Rojewski
2025-06-09 21:00 ` [PATCH 0/3] ASoC: Intel: avs: Add rt5640 board support Mark Brown
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=20250530142120.2944095-1-cezary.rojewski@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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