Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	linux-sound@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.11 109/244] ASoC: soc-pcm: Indicate warning if dpcm_playback/capture were used for availability limition
Date: Sat, 5 Oct 2024 20:29:29 -0400	[thread overview]
Message-ID: <ZwHZ6ePdG3oNRams@sashalap> (raw)
In-Reply-To: <ZvP-YQuXTyGDfb8x@finisterre.sirena.org.uk>

On Wed, Sep 25, 2024 at 02:13:21PM +0200, Mark Brown wrote:
>On Wed, Sep 25, 2024 at 07:25:30AM -0400, Sasha Levin wrote:
>> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>>
>> [ Upstream commit fd69dfe6789f4ed46d1fdb52e223cff83946d997 ]
>>
>> I have been wondering why DPCM needs special flag (= dpcm_playback/capture)
>> to use it. Below is the history why it was added to ASoC.
>
>...
>
>> Because of these history, this dpcm_xxx is unneeded flag today. But because
>> we have been used it for 10 years since (B), it may have been used
>> differently. For example some DAI available both playback/capture, but it
>> set dpcm_playback flag only, in this case dpcm_xxx flag is used as
>> availability limitation. We can use playback_only flag instead in this
>> case, but it is very difficult to find such DAI today.
>>
>> Let's add grace time to remove dpcm_playback/capture flag.
>>
>> This patch don't use dpcm_xxx flag anymore, and indicates warning to use
>> xxx_only flag if both playback/capture were available but using only
>> one of dpcm_xxx flag, and not using xxx_only flag.
>
>This is a cleanup/refactoring preparation patch, I can see no reason why
>it would be considered for stable.

Dropped, thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2024-10-06  0:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240925113641.1297102-1-sashal@kernel.org>
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 088/244] ALSA: usb-audio: Add input value sanity checks for standard types Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 091/244] ALSA: usb-audio: Support multiple control interfaces Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 092/244] ALSA: usb-audio: Define macros for quirk table entries Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 093/244] ALSA: usb-audio: Replace complex quirk lines with macros Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 094/244] ALSA: usb-audio: Add quirk for RME Digiface USB Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 095/244] ALSA: usb-audio: Add mixer " Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 096/244] ALSA: hda/realtek: Refactor and simplify Samsung Galaxy Book init Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 097/244] ALSA: usb-audio: Add logitech Audio profile quirk Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 098/244] ASoC: codecs: wsa883x: Handle reading version failure Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 099/244] ALSA: control: Take power_ref lock primarily Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 105/244] ALSA: asihpi: Fix potential OOB array access Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 106/244] ALSA: hdsp: Break infinite MIDI input flush loop Sasha Levin
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 109/244] ASoC: soc-pcm: Indicate warning if dpcm_playback/capture were used for availability limition Sasha Levin
2024-09-25 12:13   ` Mark Brown
2024-10-06  0:29     ` Sasha Levin [this message]
2024-09-25 11:25 ` [PATCH AUTOSEL 6.11 111/244] ASoC: Intel: boards: always check the result of acpi_dev_get_first_match_dev() Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZwHZ6ePdG3oNRams@sashalap \
    --to=sashal@kernel.org \
    --cc=broonie@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox