This series adds support for the idle-state property from the mux
framework to the simple-mux audio variant. It allows to specify the state
of the mux when it is not in use.

Signed-off-by: Hendrik v. Raven <h.v.raven@merzmedtech.de>
---
Changes in v2:
- Fix nullpointer dereference in simple_mux_event by accessing component
  from w->dapm instead of kcontrol.
- Link to v1: https://lore.kernel.org/r/20241114-simple-mux-idle-state-v1-0-0b082dd6549b@merzmedtech.de

---
Hendrik v. Raven (2):
      ASoc: simple-mux: add idle-state support
      ASoC: dt-bindings: simple-mux: add idle-state property

 .../bindings/sound/simple-audio-mux.yaml           |  5 +++
 sound/soc/codecs/simple-mux.c                      | 39 +++++++++++++++++++++-
 2 files changed, 43 insertions(+), 1 deletion(-)
---
base-commit: 2d5404caa8c7bb5c4e0435f94b28834ae5456623
change-id: 20241114-simple-mux-idle-state-08dd2d49e312

Best regards,
-- 
Hendrik v. Raven <h.v.raven@merzmedtech.de>

On Thu, 14 Nov 2024 12:01:24 +0100, Hendrik v. Raven wrote:
> This series adds support for the idle-state property from the mux
> framework to the simple-mux audio variant. It allows to specify the state
> of the mux when it is not in use.
> 
> 

Applied to

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

Thanks!

[1/2] ASoc: simple-mux: add idle-state support
      commit: 2b974284aa073d6e2936f9032e8ad7b99480b5b8
[2/2] ASoC: dt-bindings: simple-mux: add idle-state property
      commit: 3b7e11a0116c30848d44429650ad80f9cc3bd963

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