mbox series

[v5,0/4] ASoC: grace time for DPCM cleanup

Message ID 87bk4oqerx.wl-kuninori.morimoto.gx@renesas.com (mailing list archive)
Headers show
Series ASoC: grace time for DPCM cleanup | expand

Message

Kuninori Morimoto May 30, 2024, 1:17 a.m. UTC
Hi Mark, Pierre-Louis, Jerome
Cc each ASoC driver maintainer

This is v5 of DPCM cleanup

As we discussed in [1], we don't need to use dpcm_playback/capture flag,
so we remove it. But we have been using it for 10 years, some driver might
get damage. The most likely case is that the device/driver can use both
playback/capture, but have only one flag, and not using xxx_only flag.
[1/3] patch indicates warning in such case.

These adds grace time for DPCM cleanup.
I'm not sure when dpcm_xxx will be removed, and Codec check bypass will be
error, but maybe v6.11 or v6.12 ?
Please check each driver by that time.

Previous patch-set try to check both CPU and Codec in DPCM, but we noticed
that there are some special DAI which we can't handle today [2]. So I will
escape it in this patch-set.

[1] https://lore.kernel.org/r/87edaym2cg.wl-kuninori.morimoto.gx@renesas.com
[2] https://lore.kernel.org/all/3e67d62d-fe08-4f55-ab5b-ece8a57154f9@linux.intel.com/

Link: https://lore.kernel.org/r/87edaym2cg.wl-kuninori.morimoto.gx@renesas.com
Link: https://lore.kernel.org/r/87wmo6dyxg.wl-kuninori.morimoto.gx@renesas.com
Link: https://lore.kernel.org/r/87msole5wc.wl-kuninori.morimoto.gx@renesas.com
Link: https://lore.kernel.org/r/871q5tnuok.wl-kuninori.morimoto.gx@renesas.com

v4 -> v5
	- typo fix: limition -> limitation
	- typo fix: catpure  -> capture
	- include Intel patch

v3 -> v4
	- don't check Codec on DPCM
	- include Jerome's dpcm_xxx update patch

v2 -> v3
	- tidyup typo (reuqsts -> requests)
	- add Tested-by on git-log

v1 -> v2
	- tidyup Codec check warning output condition


Jerome Brunet (1):
  ASoC: amlogic: do not use dpcm_playback/capture flags

Kuninori Morimoto (2):
  ASoC: soc-pcm: Indicate warning if dpcm_playback/capture were used for availability limition
  ASoC: remove snd_soc_dai_link_set_capabilities()

Pierre-Louis Bossart (1):
  ASoC: Intel: sof_sdw: use playback/capture_only flags

 include/sound/soc-dai.h               |  1 -
 include/sound/soc.h                   |  1 +
 sound/soc/fsl/imx-card.c              |  3 --
 sound/soc/generic/audio-graph-card.c  |  2 -
 sound/soc/generic/audio-graph-card2.c |  2 -
 sound/soc/generic/simple-card.c       |  2 -
 sound/soc/intel/boards/sof_sdw.c      |  4 +-
 sound/soc/meson/axg-card.c            | 11 +++--
 sound/soc/meson/gx-card.c             |  1 -
 sound/soc/meson/meson-card-utils.c    |  4 +-
 sound/soc/qcom/common.c               |  1 -
 sound/soc/soc-dai.c                   | 38 ----------------
 sound/soc/soc-pcm.c                   | 65 +++++++++++++++------------
 13 files changed, 47 insertions(+), 88 deletions(-)

Comments

Mark Brown June 18, 2024, 1:20 p.m. UTC | #1
On Thu, May 30, 2024 at 01:17:39AM +0000, Kuninori Morimoto wrote:

> As we discussed in [1], we don't need to use dpcm_playback/capture flag,
> so we remove it. But we have been using it for 10 years, some driver might
> get damage. The most likely case is that the device/driver can use both
> playback/capture, but have only one flag, and not using xxx_only flag.
> [1/3] patch indicates warning in such case.

This doesn't apply against current code, please check and resend (it's
simple-card and audio-graph-card2 that conflict).
Kuninori Morimoto June 19, 2024, 4:57 a.m. UTC | #2
Hi Mark again

> > As we discussed in [1], we don't need to use dpcm_playback/capture flag,
> > so we remove it. But we have been using it for 10 years, some driver might
> > get damage. The most likely case is that the device/driver can use both
> > playback/capture, but have only one flag, and not using xxx_only flag.
> > [1/3] patch indicates warning in such case.
> 
> This doesn't apply against current code, please check and resend (it's
> simple-card and audio-graph-card2 that conflict).

Ah, I guess you used "v5 original" patch-set.
"v5 resend" patch-set or today's "v6" patch-set should be OK.

Thank you for your help !!
Best regards
---
Kuninori Morimoto
Mark Brown June 19, 2024, 11:01 a.m. UTC | #3
On Wed, Jun 19, 2024 at 04:57:22AM +0000, Kuninori Morimoto wrote:

> > This doesn't apply against current code, please check and resend (it's
> > simple-card and audio-graph-card2 that conflict).

> Ah, I guess you used "v5 original" patch-set.
> "v5 resend" patch-set or today's "v6" patch-set should be OK.

Oh, if you mark something as a resend then it sounds like it should be
exactly the same as it was before, if you've rebased you should increase
the version number.
Kuninori Morimoto June 19, 2024, 11:55 p.m. UTC | #4
Hi Mark

> > > This doesn't apply against current code, please check and resend (it's
> > > simple-card and audio-graph-card2 that conflict).
> 
> > Ah, I guess you used "v5 original" patch-set.
> > "v5 resend" patch-set or today's "v6" patch-set should be OK.
> 
> Oh, if you mark something as a resend then it sounds like it should be
> exactly the same as it was before, if you've rebased you should increase
> the version number.

Thanks, I learned it this time. Will do since next time.
And now I could understand the reason that sometime maintainer get strange
conflict which I don't have :)


Thank you for your help !!
Best regards
---
Kuninori Morimoto
Mark Brown Aug. 28, 2024, 4:29 p.m. UTC | #5
On Thu, 30 May 2024 01:17:39 +0000, Kuninori Morimoto wrote:
> Cc each ASoC driver maintainer
> 
> This is v5 of DPCM cleanup
> 
> As we discussed in [1], we don't need to use dpcm_playback/capture flag,
> so we remove it. But we have been using it for 10 years, some driver might
> get damage. The most likely case is that the device/driver can use both
> playback/capture, but have only one flag, and not using xxx_only flag.
> [1/3] patch indicates warning in such case.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: soc-pcm: Indicate warning if dpcm_playback/capture were used for availability limition
      commit: fd69dfe6789f4ed46d1fdb52e223cff83946d997
[2/4] ASoC: remove snd_soc_dai_link_set_capabilities()
      commit: 12806510481497a01d01edd64d7bb53a4d9ec28d
[3/4] ASoC: amlogic: do not use dpcm_playback/capture flags
      commit: 46fb727a28d8c7195f915150a669d927d463069b
[4/4] ASoC: Intel: sof_sdw: use playback/capture_only flags
      commit: 61e1f74f739546415570ccc1ac14e1b26afe4705

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