[PATCH v3 0/3] Improve SDCA support for duplicated features

Charles Keepax posted 3 patches 1 month, 2 weeks ago
include/sound/sdca.h                 |  4 ++
include/sound/sdca_function.h        |  1 -
include/sound/sdca_jack.h            |  3 ++
sound/soc/codecs/tas2783-sdw.c       |  6 +--
sound/soc/sdca/sdca_class.c          |  7 ---
sound/soc/sdca/sdca_class.h          |  1 -
sound/soc/sdca/sdca_class_function.c | 23 ++-------
sound/soc/sdca/sdca_functions.c      | 51 ++++++++++++-------
sound/soc/sdca/sdca_interrupts.c     |  3 +-
sound/soc/sdca/sdca_jack.c           | 75 ++++++++++++++++------------
10 files changed, 94 insertions(+), 80 deletions(-)
[PATCH v3 0/3] Improve SDCA support for duplicated features
Posted by Charles Keepax 1 month, 2 weeks ago
There are some short comings of the current SDCA class driver with
respect to duplicated functions and jacks. Fix some issues in the
reporting of jacks when there are multiple jacks represented in the SDCA
topology. When a single device contains multiple instances of the same
type of SDCA function the current class driver will create duplicate
controls, update the code to fix this. Finally whilst working through
this also tidy up the handling of the sdca_function_desc pointers as it
turns out some duplication has crept into the code on that front.

Thanks,
Charles

Changes since v2:
 - Add missing set of desc pointer in tas2783 from v1
 - Minor reordering in sdca_jack_set_jack

Changes since v1:
 - Update tas2783 for API changes
 - Correct kernel doc

Charles Keepax (3):
  ASoC: SDCA: Add correct masks whilst reporting SDCA jack status
  ASoC: SDCA: Remove sdca_function_data duplication
  ASoC: SDCA: Support devices with multiple functions of identical type

 include/sound/sdca.h                 |  4 ++
 include/sound/sdca_function.h        |  1 -
 include/sound/sdca_jack.h            |  3 ++
 sound/soc/codecs/tas2783-sdw.c       |  6 +--
 sound/soc/sdca/sdca_class.c          |  7 ---
 sound/soc/sdca/sdca_class.h          |  1 -
 sound/soc/sdca/sdca_class_function.c | 23 ++-------
 sound/soc/sdca/sdca_functions.c      | 51 ++++++++++++-------
 sound/soc/sdca/sdca_interrupts.c     |  3 +-
 sound/soc/sdca/sdca_jack.c           | 75 ++++++++++++++++------------
 10 files changed, 94 insertions(+), 80 deletions(-)

-- 
2.47.3
Re: [PATCH v3 0/3] Improve SDCA support for duplicated features
Posted by Mark Brown 1 month, 1 week ago
On Thu, 30 Apr 2026 16:09:28 +0100, Charles Keepax wrote:
> Improve SDCA support for duplicated features
> 
> There are some short comings of the current SDCA class driver with
> respect to duplicated functions and jacks. Fix some issues in the
> reporting of jacks when there are multiple jacks represented in the SDCA
> topology. When a single device contains multiple instances of the same
> type of SDCA function the current class driver will create duplicate
> controls, update the code to fix this. Finally whilst working through
> this also tidy up the handling of the sdca_function_desc pointers as it
> turns out some duplication has crept into the code on that front.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2

Thanks!

[1/3] ASoC: SDCA: Add correct masks whilst reporting SDCA jack status
      https://git.kernel.org/broonie/sound/c/cb3c257e0824
[2/3] ASoC: SDCA: Remove sdca_function_data duplication
      https://git.kernel.org/broonie/sound/c/df036250d7d5
[3/3] ASoC: SDCA: Support devices with multiple functions of identical type
      https://git.kernel.org/broonie/sound/c/250922577ed1

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark