From: "Daniel P. Berrangé" <berrange@redhat.com>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eric Blake" <eblake@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Dorinda Bassey" <dbassey@redhat.com>
Subject: Re: [PULL 1/1] audio/pwaudio.c: Add Pipewire audio backend for QEMU
Date: Fri, 5 May 2023 12:42:27 +0100 [thread overview]
Message-ID: <ZFTro47CbUGFrCyq@redhat.com> (raw)
In-Reply-To: <20230505113947.3301944-2-marcandre.lureau@redhat.com>
On Fri, May 05, 2023 at 03:39:47PM +0400, marcandre.lureau@redhat.com wrote:
> From: Dorinda Bassey <dbassey@redhat.com>
>
> This commit adds a new audiodev backend to allow QEMU to use Pipewire as
> both an audio sink and source. This backend is available on most systems
>
> Add Pipewire entry points for QEMU Pipewire audio backend
> Add wrappers for QEMU Pipewire audio backend in qpw_pcm_ops()
> qpw_write function returns the current state of the stream to pwaudio
> and Writes some data to the server for playback streams using pipewire
> spa_ringbuffer implementation.
> qpw_read function returns the current state of the stream to pwaudio and
> reads some data from the server for capture streams using pipewire
> spa_ringbuffer implementation. These functions qpw_write and qpw_read
> are called during playback and capture.
> Added some functions that convert pw audio formats to QEMU audio format
> and vice versa which would be needed in the pipewire audio sink and
> source functions qpw_init_in() & qpw_init_out().
> These methods that implement playback and recording will create streams
> for playback and capture that will start processing and will result in
> the on_process callbacks to be called.
> Built a connection to the Pipewire sound system server in the
> qpw_audio_init() method.
>
> Signed-off-by: Dorinda Bassey <dbassey@redhat.com>
> Reviewed-by: Volker Rümelin <vr_qemu@t-online.de>
> Message-Id: <20230417105654.32328-1-dbassey@redhat.com>
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> meson.build | 8 +
> qapi/audio.json | 44 ++
> audio/audio_template.h | 4 +
> audio/audio.c | 3 +
> audio/pwaudio.c | 915 ++++++++++++++++++++++++++++++++++
> audio/meson.build | 1 +
> audio/trace-events | 8 +
> meson_options.txt | 4 +-
> qemu-options.hx | 21 +
> scripts/meson-buildoptions.sh | 8 +-
> 10 files changed, 1013 insertions(+), 3 deletions(-)
> create mode 100644 audio/pwaudio.c
This doesn't add pipewire dev packages to the dockerfiles, so none of
this will get built during CI unless something else we have happens to
be pulling in pipewire dev packages indirectly.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-05-05 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 11:39 [PULL 0/1] audio patch marcandre.lureau
2023-05-05 11:39 ` [PULL 1/1] audio/pwaudio.c: Add Pipewire audio backend for QEMU marcandre.lureau
2023-05-05 11:42 ` Daniel P. Berrangé [this message]
2023-05-05 11:46 ` Marc-André Lureau
2023-05-05 21:19 ` [PULL 0/1] audio patch Richard Henderson
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=ZFTro47CbUGFrCyq@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dbassey@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).