[PATCH i-g-t 2/4] tests/intel/xe_configfs: Unbind before testing engines_allowed

[Lucas De Marchi]

Future kernel change will require the driver not to be bound yet in
order to allow this configfs setting because it has no effect
otherwise. Make sure we unbind before testing this.

Reference: https://patchwork.freedesktop.org/patch/669151/?series=151729&rev=4
Signed-off-by: Lucas De Marchi <lucas.demarchi at intel.com>
---
 tests/intel/xe_configfs.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/tests/intel/xe_configfs.c b/tests/intel/xe_configfs.c
index f01b13e13..1510f25f0 100644
--- a/tests/intel/xe_configfs.c
+++ b/tests/intel/xe_configfs.c
@@ -73,6 +73,12 @@ static void test_engines_allowed_invalid(int configfs_device_fd)
 		"rcs0asdf",
 	};
 
+	/*
+	 * These only test if engine parsing is correct, so just make sure
+	 * there's no device bind
+	 */
+	igt_kmod_unbind("xe", bus_addr);
+
 	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
 		const char *v = values[i];
 
@@ -93,6 +99,12 @@ static void test_engines_allowed(int configfs_device_fd)
 		"rcs000",
 	};
 
+	/*
+	 * These only test if engine parsing is correct, so just make sure
+	 * there's no device bind
+	 */
+	igt_kmod_unbind("xe", bus_addr);
+
 	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
 		const char *v = values[i];
 

-- 
2.50.1