These two patches were originally part of

  https://lore.kernel.org/all/20260907083727.733705-1-srinivas.kandagatla@oss.qualcomm.com/

As Suggested by Charles and Pierre am sending them as independent
of the rest of that series and can be picked up on their own.

Patch 1 adds SDCA_FUNCTION_TYPE_SIMPLE_JACK to the class function
driver's auxiliary id table so a SimpleJack auxdev is bound and
enumerated as an ASoC component, and wires set_jack for this
function type so the machine driver can register an ASoC jack
against it.

Patch 2 is a small cleanup: find_sdca_control_reset() only ever
returns 0, so convert it to void and drop the dead error check in
the caller. No functional change.

Both patches already carry Reviewed-by tags from Charles and
Pierre-Louis from the original posting.

Srinivas Kandagatla (2):
  ASoC: SDCA: register SDCA_FUNCTION_TYPE_SIMPLE_JACK in class function
    driver
  ASoC: SDCA: make find_sdca_control_reset() return void

 sound/soc/sdca/sdca_class_function.c |  5 +++++
 sound/soc/sdca/sdca_functions.c      | 12 +++++-------
 2 files changed, 10 insertions(+), 7 deletions(-)

--
2.53.0

On Tue, 08 Sep 2026 07:36:42 +0100, Srinivas Kandagatla wrote:
> ASoC: SDCA: SimpleJack support and small cleanup
> 
> These two patches were originally part of
> 
>   https://lore.kernel.org/all/20260907083727.733705-1-srinivas.kandagatla@oss.qualcomm.com/
> 
> As Suggested by Charles and Pierre am sending them as independent
> of the rest of that series and can be picked up on their own.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SDCA: register SDCA_FUNCTION_TYPE_SIMPLE_JACK in class function driver
      https://git.kernel.org/broonie/sound/c/29863d75b9f0
[2/2] ASoC: SDCA: make find_sdca_control_reset() return void
      https://git.kernel.org/broonie/sound/c/1a6a763a6237

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