[v2,0/4] Add missing dt-binding properties to rt5682(s)

Message

Nícolas F. R. A. Prado Oct. 24, 2022, 10 p.m. UTC

This series adds the missing sound-dai-cells to rt5682s and supplies for
both rt5682s and rt5682.

These properties are already used by sc7180-trogdor.dtsi (and derived
DTs like sc7180-trogdor-kingoftown.dtsi), so the commits in this series
are really just documenting their usage.

v1: https://lore.kernel.org/all/[e-mail]/

Changes in v2:
- Changed sound-dai-cells to 1 on rt5682s
- Added commit fixing sound-dai-cells on rt5682
- Added mention to commit messages that properties are already being
  used by DTs

Nícolas F. R. A. Prado (4):
  ASoC: dt-bindings: realtek,rt5682s: Add #sound-dai-cells
  ASoC: dt-bindings: realtek,rt5682s: Add AVDD and MICVDD supplies
  ASoC: dt-bindings: rt5682: Set sound-dai-cells to 1
  ASoC: dt-bindings: rt5682: Add AVDD, MICVDD and VBAT supplies

 .../devicetree/bindings/sound/realtek,rt5682s.yaml        | 7 +++++++
 Documentation/devicetree/bindings/sound/rt5682.txt        | 8 +++++++-
 2 files changed, 14 insertions(+), 1 deletion(-)

Comments

Mark Brown Oct. 26, 2022, 7:04 p.m. UTC | #1

On Mon, 24 Oct 2022 18:00:11 -0400, Nícolas F. R. A. Prado wrote:
> This series adds the missing sound-dai-cells to rt5682s and supplies for
> both rt5682s and rt5682.
> 
> These properties are already used by sc7180-trogdor.dtsi (and derived
> DTs like sc7180-trogdor-kingoftown.dtsi), so the commits in this series
> are really just documenting their usage.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: dt-bindings: realtek,rt5682s: Add #sound-dai-cells
      commit: 1c44873993d97f1da264ae9a7adb336d6af8ff9b
[3/4] ASoC: dt-bindings: rt5682: Set sound-dai-cells to 1
      commit: 07b16192f3f01d002d8ff37dcd4372980330ea93

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