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 v4 6/9] lib/igt_kmod: make it less pedantic with audio driver removal
Date: Tue, 17 May 2022 12:28:50 +0200 [thread overview]
Message-ID: <YoN44i2e83finDMl@intel.intel> (raw)
In-Reply-To: <20220517072803.186989-7-mauro.chehab@linux.intel.com>
Hi Mauro,
On Tue, May 17, 2022 at 09:28:00AM +0200, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> Current Linux Kernel don't report if the audio driver binds
> into the DRM driver. As this is CPU specific, allow audio
> driver unload fail without skipping the IGT tests on legacy
> Kernels, as this may not be mandatory.
>
> On new kernels where lsmod will properly display the dependency
> between the audio and DRM drivers, skip the core hotunplug
> test if it fails to unload the audio driver, as this is
> unrelated to the DRM driver - and it could simply because there
> are some userspace code using the audio device while the IGT
> test is running.
>
> Reviewed-by Jonathan Cavitt <jonathan.cavitt@intel.com>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thanks,
Andi
next prev parent reply other threads:[~2022-05-17 10:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 7:27 [igt-dev] [PATCH i-g-t v4 0/9] Improve logic to work with audio dependency on DRM driver Mauro Carvalho Chehab
2022-05-17 7:27 ` [igt-dev] [PATCH i-g-t v4 1/9] tests/core_hotunplug: properly finish processes using audio devices Mauro Carvalho Chehab
2022-05-17 7:27 ` [igt-dev] [PATCH i-g-t v4 2/9] lib/igt_kmod: always fill who when unloading audio driver Mauro Carvalho Chehab
2022-05-17 7:27 ` [igt-dev] [PATCH i-g-t v4 3/9] lib/igt_kmod: improve audio unbind logic Mauro Carvalho Chehab
2022-05-17 7:27 ` [igt-dev] [PATCH i-g-t v4 4/9] lib/igt_kmod: don't leak who from module unload routines Mauro Carvalho Chehab
2022-05-17 10:24 ` Andi Shyti
2022-05-17 11:04 ` Mauro Carvalho Chehab
2022-05-17 11:25 ` Petri Latvala
2022-05-17 7:27 ` [igt-dev] [PATCH i-g-t v4 5/9] core_hotunplug: fix audio unbind logic Mauro Carvalho Chehab
2022-05-17 7:28 ` [igt-dev] [PATCH i-g-t v4 6/9] lib/igt_kmod: make it less pedantic with audio driver removal Mauro Carvalho Chehab
2022-05-17 10:28 ` Andi Shyti [this message]
2022-05-17 7:28 ` [igt-dev] [PATCH i-g-t v4 7/9] lib/igt_core: export kill_children() function Mauro Carvalho Chehab
2022-05-17 10:26 ` Andi Shyti
2022-05-17 7:28 ` [igt-dev] [PATCH i-g-t v4 8/9] lib/igt_kmod: properly handle pipewire-pulse Mauro Carvalho Chehab
2022-05-17 10:34 ` Andi Shyti
2022-05-17 7:28 ` [igt-dev] [PATCH i-g-t v4 9/9] lib/igt_aux: get rid of passing pipewire-pulse pid on functions Mauro Carvalho Chehab
2022-05-17 10:53 ` Andi Shyti
2022-05-17 8:10 ` [igt-dev] ✓ Fi.CI.BAT: success for Improve logic to work with audio dependency on DRM driver Patchwork
2022-05-17 9:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=YoN44i2e83finDMl@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