[PATCH] driver core: clean driver unload
ChangeSet 1.2045, 2005/03/09 09:52:29-08:00, [EMAIL PROTECTED]
[PATCH] driver core: clean driver unload
Get rid of semaphore abuse by converting device_driver->unload_sem
semaphore to device_driver->unloaded completion.
This should get rid of any confusion as well as save a few bytes in the
process.
Signed-off-by: Mike Waychison <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
drivers/base/bus.c |2 +-
drivers/base/driver.c | 13 ++---
include/linux/device.h |2 +-
3 files changed, 8 insertions(+), 9 deletions(-)
diff -Nru a/drivers/base/bus.c b/drivers/base/bus.c
--- a/drivers/base/bus.c2005-03-09 16:29:14 -08:00
+++ b/drivers/base/bus.c2005-03-09 16:29:14 -08:00
@@ -65,7 +65,7 @@
static void driver_release(struct kobject * kobj)
{
struct device_driver * drv = to_driver(kobj);
- up(>unload_sem);
+ complete(>unloaded);
}
static struct kobj_type ktype_driver = {
diff -Nru a/drivers/base/driver.c b/drivers/base/driver.c
--- a/drivers/base/driver.c 2005-03-09 16:29:14 -08:00
+++ b/drivers/base/driver.c 2005-03-09 16:29:14 -08:00
@@ -79,14 +79,14 @@
* since most of the things we have to do deal with the bus
* structures.
*
- * The one interesting aspect is that we initialize @drv->unload_sem
- * to a locked state here. It will be unlocked when the driver
- * reference count reaches 0.
+ * The one interesting aspect is that we setup @drv->unloaded
+ * as a completion that gets complete when the driver reference
+ * count reaches 0.
*/
int driver_register(struct device_driver * drv)
{
INIT_LIST_HEAD(>devices);
- init_MUTEX_LOCKED(>unload_sem);
+ init_completion(>unloaded);
return bus_add_driver(drv);
}
@@ -97,7 +97,7 @@
*
* Again, we pass off most of the work to the bus-level call.
*
- * Though, once that is done, we attempt to take @drv->unload_sem.
+ * Though, once that is done, we wait until @drv->unloaded is completed.
* This will block until the driver refcount reaches 0, and it is
* released. Only modular drivers will call this function, and we
* have to guarantee that it won't complete, letting the driver
@@ -107,8 +107,7 @@
void driver_unregister(struct device_driver * drv)
{
bus_remove_driver(drv);
- down(>unload_sem);
- up(>unload_sem);
+ wait_for_completion(>unloaded);
}
/**
diff -Nru a/include/linux/device.h b/include/linux/device.h
--- a/include/linux/device.h2005-03-09 16:29:14 -08:00
+++ b/include/linux/device.h2005-03-09 16:29:14 -08:00
@@ -102,7 +102,7 @@
char* name;
struct bus_type * bus;
- struct semaphoreunload_sem;
+ struct completion unloaded;
struct kobject kobj;
struct list_headdevices;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] driver core: clean driver unload
ChangeSet 1.2045, 2005/03/09 09:52:29-08:00, [EMAIL PROTECTED]
[PATCH] driver core: clean driver unload
Get rid of semaphore abuse by converting device_driver-unload_sem
semaphore to device_driver-unloaded completion.
This should get rid of any confusion as well as save a few bytes in the
process.
Signed-off-by: Mike Waychison [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
drivers/base/bus.c |2 +-
drivers/base/driver.c | 13 ++---
include/linux/device.h |2 +-
3 files changed, 8 insertions(+), 9 deletions(-)
diff -Nru a/drivers/base/bus.c b/drivers/base/bus.c
--- a/drivers/base/bus.c2005-03-09 16:29:14 -08:00
+++ b/drivers/base/bus.c2005-03-09 16:29:14 -08:00
@@ -65,7 +65,7 @@
static void driver_release(struct kobject * kobj)
{
struct device_driver * drv = to_driver(kobj);
- up(drv-unload_sem);
+ complete(drv-unloaded);
}
static struct kobj_type ktype_driver = {
diff -Nru a/drivers/base/driver.c b/drivers/base/driver.c
--- a/drivers/base/driver.c 2005-03-09 16:29:14 -08:00
+++ b/drivers/base/driver.c 2005-03-09 16:29:14 -08:00
@@ -79,14 +79,14 @@
* since most of the things we have to do deal with the bus
* structures.
*
- * The one interesting aspect is that we initialize @drv-unload_sem
- * to a locked state here. It will be unlocked when the driver
- * reference count reaches 0.
+ * The one interesting aspect is that we setup @drv-unloaded
+ * as a completion that gets complete when the driver reference
+ * count reaches 0.
*/
int driver_register(struct device_driver * drv)
{
INIT_LIST_HEAD(drv-devices);
- init_MUTEX_LOCKED(drv-unload_sem);
+ init_completion(drv-unloaded);
return bus_add_driver(drv);
}
@@ -97,7 +97,7 @@
*
* Again, we pass off most of the work to the bus-level call.
*
- * Though, once that is done, we attempt to take @drv-unload_sem.
+ * Though, once that is done, we wait until @drv-unloaded is completed.
* This will block until the driver refcount reaches 0, and it is
* released. Only modular drivers will call this function, and we
* have to guarantee that it won't complete, letting the driver
@@ -107,8 +107,7 @@
void driver_unregister(struct device_driver * drv)
{
bus_remove_driver(drv);
- down(drv-unload_sem);
- up(drv-unload_sem);
+ wait_for_completion(drv-unloaded);
}
/**
diff -Nru a/include/linux/device.h b/include/linux/device.h
--- a/include/linux/device.h2005-03-09 16:29:14 -08:00
+++ b/include/linux/device.h2005-03-09 16:29:14 -08:00
@@ -102,7 +102,7 @@
char* name;
struct bus_type * bus;
- struct semaphoreunload_sem;
+ struct completion unloaded;
struct kobject kobj;
struct list_headdevices;
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
