From: Vinod Koul <vkoul@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: "Linux Sound ML" <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.dev>
Subject: Re: [PATCH v6] ALSA: compress_offload: introduce accel operation mode
Date: Wed, 23 Oct 2024 10:57:13 +0530 [thread overview]
Message-ID: <ZxiJMQkbA9MhtjXF@vaman> (raw)
In-Reply-To: <20241002093904.1809799-1-perex@perex.cz>
Hi Jaroslav,
On 02-10-24, 11:39, Jaroslav Kysela wrote:
> There is a requirement to expose the audio hardware that accelerates various
> tasks for user space such as sample rate converters, compressed
> stream decoders, etc.
>
> This is description for the API extension for the compress ALSA API which
> is able to handle "tasks" that are not bound to real-time operations
> and allows for the serialization of operations.
This lgtm, but I found one thing missing. I think we had
discussed that we might want to call the devices with accel api not
ComprCxDy but something else? Can we add that.. maybe accelCxDy instead
as both are mutually exclusive
--
~Vinod
next prev parent reply other threads:[~2024-10-23 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 9:39 [PATCH v6] ALSA: compress_offload: introduce accel operation mode Jaroslav Kysela
2024-10-09 8:51 ` Shengjiu Wang
2024-10-22 14:15 ` Takashi Iwai
2024-10-22 14:17 ` Mark Brown
2024-10-25 8:57 ` Takashi Iwai
2024-10-25 9:15 ` Shengjiu Wang
2024-10-25 9:40 ` Takashi Iwai
2024-10-22 14:31 ` Amadeusz Sławiński
2024-10-23 5:27 ` Vinod Koul [this message]
2024-10-23 5:43 ` 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=ZxiJMQkbA9MhtjXF@vaman \
--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.dev \
--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