Re: [PATCH] ACPI: make acpi_bus_register_driver() return zero for success, not device count

[Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>]

Thus wrote Bjorn Helgaas:
> > True.  But your driver can use its own mechanism to determine whether
> > it claimed any devices, and if not, call acpi_bus_unregister_driver()
> > and then return -ENODEV from the module init function to cause the
> > module to be unloaded.
> Here's what I had in mind (untested).  Would something like this
> address your concern?

It's clunky, but yes, at least until something better (say, sysfs support
for ACPI) goes in. Note that I'm on vacation till monday, so I won't be able
to test it either.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org

Acked-by: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>


Index: work/drivers/acpi/asus_acpi.c
===================================================================
--- work.orig/drivers/acpi/asus_acpi.c	2005-07-27 13:52:21.000000000 -0600
+++ work/drivers/acpi/asus_acpi.c	2005-07-28 09:56:17.000000000 -0600
@@ -1111,6 +1111,8 @@
 }
 
 
+static int __init asus_found;
+
 static int __init asus_hotk_add(struct acpi_device *device)
 {
 	acpi_status status = AE_OK;
@@ -1168,6 +1170,8 @@
 		}
 	}
 
+	asus_found = 1;
+
       end:
 	if (result) {
 		kfree(hotk);
@@ -1221,6 +1225,12 @@
 		return -ENODEV;
 	}
 
+	if (!asus_found) {
+		acpi_bus_unregister_driver(&asus_hotk_driver);
+		remove_proc_entry(PROC_ASUS, acpi_root_dir);
+		return -ENODEV;
+	}
+
 	return 0;
 }
 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf