From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.dev, shenghao-ding@ti.com,
kevin-lu@ti.com, baojun.xu@ti.com, sen@ti.com,
niranjan.hy@ti.com, oder_chiou@realtek.com, shumingf@realtek.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: [PATCH 0/8] Reword the SDCA HID code
Date: Wed, 5 Aug 2026 13:41:57 +0100 [thread overview]
Message-ID: <20260805124205.4152543-1-ckeepax@opensource.cirrus.com> (raw)
This series reworks the SDCA HID code, the primary goals being to no
longer store runtime HID data in the DisCo data structures and remove
the need to pass the soundwire device into the ACPI parsing code.
To achieve this the HID device registration is moved to the IRQ work
flow rather than the ACPI work flow.
Also a few small issues are fixed up along the way, some formatting,
some missing cleanup/docs.
Thanks,
Charles
Charles Keepax (8):
ASoC: SDCA: Tidy up error message
ASoC: SDCA: Remove unused dev pointer argument
ASoC: SDCA: Move HID registration to IRQ time
ASoC: SDCA: Move HID descriptors to function
ASoC: SDCA: Update HID DisCo parsing
ASoC: SDCA: Add missing destroy for HID device
ASoC: SDCA: Add missing HID kernel doc
ASoC: SDCA: Pass swft table through sdca_dev_register()
include/sound/sdca_asoc.h | 8 +-
include/sound/sdca_function.h | 24 ++--
include/sound/sdca_hid.h | 11 +-
sound/soc/codecs/rt766-sdca.c | 26 +++-
sound/soc/codecs/rt766-sdca.h | 2 +
sound/soc/codecs/tac5xx2-sdw.c | 6 +-
sound/soc/codecs/tas2783-sdw.c | 2 +-
sound/soc/sdca/sdca_asoc.c | 13 +-
sound/soc/sdca/sdca_class_function.c | 2 +-
sound/soc/sdca/sdca_function_device.c | 7 +-
sound/soc/sdca/sdca_functions.c | 180 +++++++++++++++-----------
sound/soc/sdca/sdca_hid.c | 48 ++++---
sound/soc/sdca/sdca_interrupts.c | 6 +
13 files changed, 211 insertions(+), 124 deletions(-)
--
2.47.3
next reply other threads:[~2026-08-05 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 12:41 Charles Keepax [this message]
2026-08-05 12:41 ` [PATCH 1/8] ASoC: SDCA: Tidy up error message Charles Keepax
2026-08-05 12:41 ` [PATCH 2/8] ASoC: SDCA: Remove unused dev pointer argument Charles Keepax
2026-08-05 12:42 ` [PATCH 3/8] ASoC: SDCA: Move HID registration to IRQ time Charles Keepax
2026-08-05 12:42 ` [PATCH 4/8] ASoC: SDCA: Move HID descriptors to function Charles Keepax
2026-08-05 12:42 ` [PATCH 5/8] ASoC: SDCA: Update HID DisCo parsing Charles Keepax
2026-08-05 12:42 ` [PATCH 6/8] ASoC: SDCA: Add missing destroy for HID device Charles Keepax
2026-08-05 12:42 ` [PATCH 7/8] ASoC: SDCA: Add missing HID kernel doc Charles Keepax
2026-08-05 12:42 ` [PATCH 8/8] ASoC: SDCA: Pass swft table through sdca_dev_register() Charles Keepax
2026-08-06 8:57 ` [PATCH 0/8] Reword the SDCA HID code Pierre-Louis Bossart
2026-08-06 12:42 ` 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=20260805124205.4152543-1-ckeepax@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=niranjan.hy@ti.com \
--cc=oder_chiou@realtek.com \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=shumingf@realtek.com \
--cc=yung-chuan.liao@linux.intel.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