From: Cezary Rojewski <cezary.rojewski@intel.com>
To: broonie@kernel.org
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
tiwai@suse.com, perex@perex.cz,
amadeuszx.slawinski@linux.intel.com,
pierre-louis.bossart@linux.intel.com, hdegoede@redhat.com,
cujomalainey@chromium.org, lmajczak@google.com,
Cezary Rojewski <cezary.rojewski@intel.com>
Subject: [PATCH 0/4] ASoC: Drop soc-topology ABI v4 support
Date: Wed, 3 Apr 2024 11:16:25 +0200 [thread overview]
Message-ID: <20240403091629.647267-1-cezary.rojewski@intel.com> (raw)
This patchset impacts UAPI.
The only known users of the soc-topology ABI v4 are Chromebook
configurations. Starting from kernel v5.4, all of them are making use of
soc-topology ABI v5. The patchset first removes obsolete code from the
Intel's skylake-driver - the driver of choice for the mentioned
Chromebooks - and then proceeds with removal of relevant soc-topology.c
and uapi bits.
Cezary Rojewski (4):
ASoC: Intel: Skylake: Remove soc-topology ABI v4 support
ASoC: topology: Remove ABI v4 support
ASoC: topology: Cleanup after ABI v4 support removal
ASoC: topology: Remove obsolete ABI v4 structs
include/uapi/sound/asoc.h | 56 ------
include/uapi/sound/skl-tplg-interface.h | 74 --------
sound/soc/intel/skylake/skl-topology.c | 169 -----------------
sound/soc/soc-topology.c | 241 ++----------------------
4 files changed, 18 insertions(+), 522 deletions(-)
--
2.25.1
next reply other threads:[~2024-04-03 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 9:16 Cezary Rojewski [this message]
2024-04-03 9:16 ` [PATCH 1/4] ASoC: Intel: Skylake: Remove soc-topology ABI v4 support Cezary Rojewski
2024-04-03 9:16 ` [PATCH 2/4] ASoC: topology: Remove " Cezary Rojewski
2024-04-03 9:16 ` [PATCH 3/4] ASoC: topology: Cleanup after ABI v4 support removal Cezary Rojewski
2024-04-03 9:16 ` [PATCH 4/4] ASoC: topology: Remove obsolete ABI v4 structs Cezary Rojewski
2024-04-03 15:53 ` [PATCH 0/4] ASoC: Drop soc-topology ABI v4 support Mark Brown
2024-04-04 14:31 ` Cezary Rojewski
2024-04-04 18:03 ` 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=20240403091629.647267-1-cezary.rojewski@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=hdegoede@redhat.com \
--cc=linux-sound@vger.kernel.org \
--cc=lmajczak@google.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--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