From: Andi Shyti <andi.shyti@linux.intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org,
Ch Sai Gowtham <sai.gowtham.ch@intel.com>,
Petri Latvala <petri.latvala@intel.com>,
Andrzej Hajda <andrzej.hajda@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v3 1/6] tests/core_hotunplug: properly finish processes using audio devices
Date: Mon, 16 May 2022 14:31:38 +0200 [thread overview]
Message-ID: <YoJEKqVBQHT0WCHP@intel.intel> (raw)
In-Reply-To: <20220506114829.2288273-2-mauro.chehab@linux.intel.com>
Hi Mauro,
On Fri, May 06, 2022 at 01:48:24PM +0200, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> Before unloading or unbinding an audio driver, all processes
> that are using it must be terminated. The current logic seeks
> only for alsactl, but ignore other processes, including
> pulseaudio.
>
> Make the logic more general, extending it to any processes that
> could have an open device under /dev/snd.
>
> It should be noticed that some distros like Fedora and openSUSE
> are now migrating from pulseaudio into pipewire-pulse. Right
> now, there's no standard distribution-agnostic way to request
> pipewire-pulse to stop using audio devices, but there's a new
> patch upstream that will make things easier:
>
> https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/6ad6300ec657c88322a8cd6f3548261d3dc05359
>
> Which should be available for pipewire-pulse versions 0.3.50 and
> upper.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
next prev parent reply other threads:[~2022-05-16 12:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 11:48 [igt-dev] [PATCH i-g-t v3 0/6] Improve logic to work with audio dependency on DRM driver Mauro Carvalho Chehab
2022-05-06 11:48 ` [igt-dev] [PATCH i-g-t v3 1/6] tests/core_hotunplug: properly finish processes using audio devices Mauro Carvalho Chehab
2022-05-11 17:03 ` Lucas De Marchi
2022-05-12 6:49 ` Mauro Carvalho Chehab
2022-05-16 7:24 ` Lucas De Marchi
2022-05-16 8:04 ` Mauro Carvalho Chehab
2022-05-16 12:31 ` Andi Shyti [this message]
2022-05-06 11:48 ` [igt-dev] [PATCH i-g-t v3 2/6] lib/igt_kmod: always fill who when unloading audio driver Mauro Carvalho Chehab
2022-05-06 11:48 ` [igt-dev] [PATCH i-g-t v3 3/6] lib/igt_kmod: improve audio unbind logic Mauro Carvalho Chehab
2022-05-11 17:09 ` Lucas De Marchi
2022-05-16 6:55 ` Mauro Carvalho Chehab
2022-05-16 12:30 ` Andi Shyti
2022-05-16 13:23 ` Mauro Carvalho Chehab
2022-05-06 11:48 ` [igt-dev] [PATCH i-g-t v3 4/6] core_hotunplug: fix " Mauro Carvalho Chehab
2022-05-06 11:48 ` [igt-dev] [PATCH i-g-t v3 5/6] lib/igt_kmod: make it less pedantic with audio driver removal Mauro Carvalho Chehab
2022-05-06 11:48 ` [igt-dev] [PATCH i-g-t v3 6/6] lib/igt_kmod: properly handle pipewire-pulse Mauro Carvalho Chehab
2022-05-16 12:49 ` Andi Shyti
2022-05-16 13:35 ` Mauro Carvalho Chehab
2022-05-16 16:51 ` Mauro Carvalho Chehab
2022-05-06 12:10 ` [igt-dev] ✓ Fi.CI.BAT: success for Improve logic to work with audio dependency on DRM driver Patchwork
2022-05-06 14:23 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=YoJEKqVBQHT0WCHP@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mauro.chehab@linux.intel.com \
--cc=petri.latvala@intel.com \
--cc=sai.gowtham.ch@intel.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