From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH RFC] ASoC: amlogic: do not use dpcm_playback/capture flags
Date: Tue, 14 May 2024 15:45:26 +0100 [thread overview]
Message-ID: <46daae9b-10dc-4f49-8a25-c387d03ae87a@sirena.org.uk> (raw)
In-Reply-To: <20240514143116.3824376-1-jbrunet@baylibre.com>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
On Tue, May 14, 2024 at 04:30:46PM +0200, Jerome Brunet wrote:
> dpcm_playback/capture flags are being deprecated in ASoC.
> Use playback/capture_only flags instead
>
> Suggested-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
>
> Following Kuninori's series, dpcm_playback/capture will be ignored.
> However, properly disabling stream direction is important for Amlogic
> audio drivers.
>
> I'm not too sure how this should be applied to avoid breaking bisect,
> before or after Kuninori's series. Maybe it should be merged into it ?
Probably better to integrate it I think?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-05-14 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o79azh65.wl-kuninori.morimoto.gx@renesas.com>
2024-05-14 14:30 ` [PATCH RFC] ASoC: amlogic: do not use dpcm_playback/capture flags Jerome Brunet
2024-05-14 14:45 ` Mark Brown [this message]
2024-05-14 23:11 ` Kuninori Morimoto
2024-05-15 13:01 ` Jerome Brunet
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=46daae9b-10dc-4f49-8a25-c387d03ae87a@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jbrunet@baylibre.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).