Linux Sound subsystem development
 help / color / mirror / Atom feed
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: Tue, 2 Jul 2024 19:21:22 +0530	[thread overview]
Message-ID: <ZoQF2qjLf7_00yA7@matsya> (raw)
In-Reply-To: <ae18019b-5e6f-4ca8-8fba-353ed19be46c@perex.cz>


Hi Jaroslav,

On 24-06-24, 17:31, Jaroslav Kysela wrote:
> On 24. 06. 24 16:47, Vinod Koul wrote:
> > On 24-06-24, 15:58, 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.
> > 
> > Can you please tell me more about this requirement. The initial view of
> > compressed API was data only and use alsa kcontrols to handle the DSP
> > functions? I would like to understand why we need a new API.
> 
> There are very long threads for v4l audio support - last v15 thread:
> 
> https://lore.kernel.org/linux-media/1710834674-3285-1-git-send-email-shengjiu.wang@nxp.com/

Very long indeed but very interesting. I think going compressed audio
way seems reasonable choice to me

> 
> So the goal is to create something more efficient for the offload work, when
> the data (decoded/converted) should be returned back to the user space.

Not rendered? so we are using it as an accelerator...?

> 
> > 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?

> 
> > > +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.. Also do we change the device name if the passthru is
enabled? it should not be called a playback or capture compressed device

-- 
~Vinod

  reply	other threads:[~2024-07-02 13:51 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 [this message]
2024-07-12 16:45       ` Jaroslav Kysela
2024-07-15  6:22         ` Vinod Koul
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=ZoQF2qjLf7_00yA7@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