From: Takashi Iwai <tiwai@suse.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
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,
broonie@kernel.org, sakari.ailus@iki.fi, festevam@gmail.com,
perex@perex.cz, mchehab@kernel.org, shengjiu.wang@gmail.com,
m.szyprowski@samsung.com
Subject: Re: [RFC PATCH v2 0/7] Add audio support in v4l2 framework
Date: Wed, 02 Aug 2023 13:22:51 +0200 [thread overview]
Message-ID: <87il9xu1ro.wl-tiwai@suse.de> (raw)
In-Reply-To: <47d66c28-1eb2-07f5-d6f9-779d675aefe8@xs4all.nl>
On Wed, 02 Aug 2023 09:32:37 +0200,
Hans Verkuil wrote:
>
> Hi all,
>
> On 25/07/2023 08:12, Shengjiu Wang wrote:
> > Audio signal processing has the requirement for memory to
> > memory similar as Video.
> >
> > This patch is to add this support in v4l2 framework, defined
> > new buffer type V4L2_BUF_TYPE_AUDIO_CAPTURE and
> > V4L2_BUF_TYPE_AUDIO_OUTPUT, defined new format v4l2_audio_format
> > for audio case usage.
> >
> > The created audio device is named "/dev/audioX".
> >
> > And add memory to memory support for two kinds of i.MX ASRC
> > module
>
> Before I spend time on this: are the audio maintainers OK with doing
> this in V4L2?
>
> I do want to have a clear statement on this as it is not something I
> can decide.
Well, I personally don't mind to have some audio capability in v4l2
layer. But, the only uncertain thing for now is whether this is a
must-have or not.
IIRC, the implementation in the sound driver side was never done just
because there was no similar implementation? If so, and if the
extension to the v4l2 core layer is needed, shouldn't it be more
considered for the possible other route?
thanks,
Takashi
next prev parent reply other threads:[~2023-08-02 11:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:12 [RFC PATCH v2 0/7] Add audio support in v4l2 framework Shengjiu Wang
2023-07-25 6:12 ` [RFC PATCH v2 1/7] ASoC: fsl_asrc: define functions for memory to memory usage Shengjiu Wang
2023-08-01 13:58 ` Daniel Baluta
2023-07-25 6:12 ` [RFC PATCH v2 2/7] ASoC: fsl_easrc: " Shengjiu Wang
2023-07-25 6:12 ` [RFC PATCH v2 3/7] ASoC: fsl_asrc: move fsl_asrc_common.h to include/sound Shengjiu Wang
2023-07-25 6:12 ` [RFC PATCH v2 4/7] media: v4l2: Add audio capture and output support Shengjiu Wang
2023-07-28 7:59 ` Tomasz Figa
2023-07-28 15:24 ` Mark Brown
2023-07-31 8:05 ` Shengjiu Wang
2023-08-01 9:47 ` Shengjiu Wang
2023-08-02 7:19 ` Tomasz Figa
2023-07-25 6:12 ` [RFC PATCH v2 5/7] media: imx: fsl_asrc: Add memory to memory driver Shengjiu Wang
2023-08-01 14:15 ` Daniel Baluta
2023-07-25 6:12 ` [RFC PATCH v2 6/7] ASoC: fsl_asrc: register m2m platform device Shengjiu Wang
2023-07-25 6:12 ` [RFC PATCH v2 7/7] ASoC: fsl_easrc: " Shengjiu Wang
2023-08-02 7:32 ` [RFC PATCH v2 0/7] Add audio support in v4l2 framework Hans Verkuil
2023-08-02 11:22 ` Takashi Iwai [this message]
2023-08-02 12:02 ` Shengjiu Wang
2023-08-02 12:08 ` Takashi Iwai
2023-08-02 14:41 ` Shengjiu Wang
2023-08-02 17:28 ` Mark Brown
2023-08-03 13:11 ` Shengjiu Wang
2023-08-11 11:05 ` Shengjiu Wang
2023-08-23 14:33 ` Shengjiu Wang
2023-08-24 17:03 ` Takashi Iwai
2023-08-24 20:21 ` Mark Brown
2023-08-25 3:46 ` Shengjiu Wang
2023-08-25 13:54 ` Takashi Iwai
2023-08-25 14:15 ` Hans Verkuil
2023-08-30 3:11 ` Shengjiu Wang
2023-08-31 20:41 ` Nicolas Dufresne
2023-08-02 12:09 ` Mark Brown
2023-08-02 12:28 ` Hans Verkuil
2023-08-04 12:19 ` Shengjiu Wang
2023-08-04 12:34 ` Hans Verkuil
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=87il9xu1ro.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=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).