From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.com, vkoul@kernel.org,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
peter.ujfalusi@linux.intel.com, shumingf@realtek.com,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com
Subject: [PATCH 0/3] SDCA Jack Fixups
Date: Mon, 15 Dec 2025 15:36:46 +0000 [thread overview]
Message-ID: <20251215153650.3913117-1-ckeepax@opensource.cirrus.com> (raw)
Some fixups to the jack handling, adding some necessary hooks to connect
things with the machine driver. I have split these out from the system
suspend chain as that has been generating a fair amount of discussion
and getting these 3 merged is far more important to get basic
functionality working smoothly. I will do a spin of the system suspend
stuff soon, if either no new comments pop up, or we reach some consensus
on how to proceed.
Thanks,
Charles
Charles Keepax (3):
ASoC: SDCA: Factor out jack handling into new c file
ASoC: SDCA: Add ability to connect SDCA jacks to ASoC jacks
ASoC: SDCA: Add ASoC jack hookup in class driver
include/sound/sdca_jack.h | 32 ++++
sound/soc/sdca/Makefile | 2 +-
sound/soc/sdca/sdca_class_function.c | 13 ++
sound/soc/sdca/sdca_interrupts.c | 83 +--------
sound/soc/sdca/sdca_jack.c | 244 +++++++++++++++++++++++++++
5 files changed, 297 insertions(+), 77 deletions(-)
create mode 100644 include/sound/sdca_jack.h
create mode 100644 sound/soc/sdca/sdca_jack.c
--
2.47.3
next reply other threads:[~2025-12-15 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 15:36 Charles Keepax [this message]
2025-12-15 15:36 ` [PATCH RESEND 1/3] ASoC: SDCA: Factor out jack handling into new c file Charles Keepax
2025-12-15 15:36 ` [PATCH RESEND 2/3] ASoC: SDCA: Add ability to connect SDCA jacks to ASoC jacks Charles Keepax
2025-12-15 15:36 ` [PATCH RESEND 3/3] ASoC: SDCA: Add ASoC jack hookup in class driver Charles Keepax
2025-12-19 1:58 ` [PATCH 0/3] SDCA Jack Fixups Liao, Bard
2025-12-22 20:58 ` 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=20251215153650.3913117-1-ckeepax@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=shumingf@realtek.com \
--cc=vkoul@kernel.org \
--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