From: Vinod Koul <vkoul@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: linux-sound@vger.kernel.org, "Takashi Iwai" <tiwai@suse.de>,
"Mark Brown" <broonie@kernel.org>,
"Shengjiu Wang" <shengjiu.wang@gmail.com>,
"Nicolas Dufresne" <nicolas@ndufresne.ca>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v4] ALSA: compress_offload: introduce passthrough operation mode
Date: Mon, 15 Jul 2024 11:52:50 +0530 [thread overview]
Message-ID: <ZpTAOhsQE0Eh2Yz8@matsya> (raw)
In-Reply-To: <a89f3755-9b21-41b5-9b15-73105d4e6b95@perex.cz>
On 12-07-24, 18:45, Jaroslav Kysela wrote:
> On 02. 07. 24 15:51, Vinod Koul wrote:
> > > > What about the user of this API, i would like to see that as well
> > >
> > > Any audio streaming framework like gstreamer or ffmpeg who can accelerate
> > > stream conversions in hardware for capable devices.
> >
> > I meant to see driver users along with this patch :-)
> >
> > That also reminds me to ask about usermode support for this, are you
> > planning to support it in tinycompress?
>
> Yes, I do, but my time is limited in the next weeks, but it's on my to-do list.
>
> > > > > +A new direction SND_COMPRESS_PASSTHROUGH is introduced to identify
> > > > > +the passthrough API.
> > > >
> > > > Is passthrough really a new good new name, this suggests data being
> > > > passed thru but that is not the case...
> > >
> > > It's something like "PASS data THROUGH kernel/driver". So it makes sense. My
> > > alternate name may be ACCEL (like acceleration).
> >
> > I like that..
>
> To clarify, are you speaking about "passthrough" or "accel" here?
Confirming that I would prefer 'accel' here and probably not to confuse
with new 'accel' subsystem maybe compr_accel or something.. Better
suggestions?
--
~Vinod
next prev parent reply other threads:[~2024-07-15 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 13:58 [PATCH v4] ALSA: compress_offload: introduce passthrough operation mode Jaroslav Kysela
2024-06-24 14:47 ` Vinod Koul
2024-06-24 15:31 ` Jaroslav Kysela
2024-07-02 13:51 ` Vinod Koul
2024-07-12 16:45 ` Jaroslav Kysela
2024-07-15 6:22 ` Vinod Koul [this message]
2024-06-24 15:01 ` Amadeusz Sławiński
2024-06-24 15:41 ` Jaroslav Kysela
2024-07-12 3:38 ` Shengjiu Wang
2024-07-12 16:45 ` Jaroslav Kysela
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=ZpTAOhsQE0Eh2Yz8@matsya \
--to=vkoul@kernel.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shengjiu.wang@gmail.com \
--cc=tiwai@suse.de \
/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