From: Takashi Iwai <tiwai@suse.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
Jacopo Mondi <jacopo@jmondi.org>,
Xiubo.Lee@gmail.com, linux-kernel@vger.kernel.org,
Shengjiu Wang <shengjiu.wang@nxp.com>,
tiwai@suse.com, linux-media@vger.kernel.org, tfiga@chromium.org,
nicoleotsuka@gmail.com, linuxppc-dev@lists.ozlabs.org,
Mark Brown <broonie@kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
festevam@gmail.com, perex@perex.cz, mchehab@kernel.org,
Shengjiu Wang <shengjiu.wang@gmail.com>,
m.szyprowski@samsung.com
Subject: Re: [PATCH 1/6] media: v4l2: Add audio capture and output support
Date: Mon, 03 Jul 2023 15:25:04 +0200 [thread overview]
Message-ID: <8735255dqn.wl-tiwai@suse.de> (raw)
In-Reply-To: <d78e6ec3-a531-8fd4-a785-29b6712f83ae@xs4all.nl>
On Mon, 03 Jul 2023 15:12:55 +0200,
Hans Verkuil wrote:
>
> On 03/07/2023 14:53, Mark Brown wrote:
> > On Mon, Jul 03, 2023 at 02:07:10PM +0200, Takashi Iwai wrote:
> >> Shengjiu Wang wrote:
> >
> >>> There is no such memory to memory interface defined in ALSA. Seems
> >>> ALSA is not designed for M2M cases.
> >
> >> There is no restriction to implement memory-to-memory capture in ALSA
> >> framework. It'd be a matter of the setup of PCM capture source, and
> >> you can create a corresponding kcontrol element to switch the mode or
> >> assign a dedicated PCM substream, for example. It's just that there
> >> was little demand for that.
> >
> > Yeah, it's not a terrible idea. We might use it more if we ever get
> > better support for DSP audio, routing between the DSP and external
> > devices if driven from the CPU would be a memory to memory thing.
> >
> >> I'm not much against adding the audio capture feature to V4L2,
> >> though, if it really makes sense. But creating a crafted /dev/audio*
> >> doesn't look like a great idea to me, at least.
> >
> > I've still not looked at the code at all.
>
> My main concern is that these cross-subsystem drivers are a pain to
> maintain. So there have to be good reasons to do this.
>
> Also it is kind of weird to have to use the V4L2 API in userspace to
> deal with a specific audio conversion. Quite unexpected.
>
> But in the end, that's a decision I can't make.
>
> So I wait for that feedback. Note that if the decision is made that this
> can use V4L2, then there is quite a lot more that needs to be done:
> documentation, new compliance tests, etc. It's adding a new API, and that
> comes with additional work...
All agreed. Especially in this case, it doesn't have to be in V4L2
API, as it seems.
(Though, the support of audio on V4L2 might be useful if it's closely
tied with the a stream. But that's another story.)
thanks,
Takashi
next prev parent reply other threads:[~2023-07-03 13:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 1:37 [PATCH 0/6] Add audio support in v4l2 framework Shengjiu Wang
2023-06-29 1:37 ` [PATCH 1/6] media: v4l2: Add audio capture and output support Shengjiu Wang
2023-06-30 10:05 ` Sakari Ailus
2023-07-03 9:54 ` Shengjiu Wang
2023-07-03 10:04 ` Hans Verkuil
2023-07-03 12:07 ` Takashi Iwai
2023-07-03 12:53 ` Mark Brown
2023-07-03 13:12 ` Hans Verkuil
2023-07-03 13:25 ` Takashi Iwai [this message]
2023-07-04 3:55 ` Shengjiu Wang
2023-07-03 17:58 ` Mark Brown
2023-07-04 4:03 ` Shengjiu Wang
2023-07-07 3:13 ` Shengjiu Wang
2023-07-19 9:15 ` Shengjiu Wang
2023-06-29 1:37 ` [PATCH 2/6] ASoC: fsl_asrc: define functions for memory to memory usage Shengjiu Wang
2023-06-29 1:37 ` [PATCH 3/6] ASoC: fsl_easrc: " Shengjiu Wang
2023-06-29 10:59 ` Fabio Estevam
2023-06-30 3:23 ` Shengjiu Wang
2023-06-29 1:37 ` [PATCH 4/6] ASoC: fsl_asrc: Add memory to memory driver Shengjiu Wang
2023-06-29 11:38 ` Mark Brown
2023-06-30 3:37 ` Shengjiu Wang
2023-06-30 11:22 ` Mark Brown
2023-06-29 1:37 ` [PATCH 5/6] ASoC: fsl_asrc: enable memory to memory function Shengjiu Wang
2023-06-29 1:37 ` [PATCH 6/6] ASoC: fsl_easrc: " Shengjiu Wang
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=8735255dqn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo@jmondi.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=sakari.ailus@iki.fi \
--cc=shengjiu.wang@gmail.com \
--cc=shengjiu.wang@nxp.com \
--cc=tfiga@chromium.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;
as well as URLs for NNTP newsgroup(s).