kernel/linux.git/drivers/base/dd.c, branch linux-2.6.28.y

device model: Do a quickcheck for driver binding before doing an expensive check

2008-10-16T16:24:50+00:00

This patch adds a quick check for the driver<->device match before taking the locks and doin gthe expensive checks. Taking the lock hurts in asynchronous boot context where the device lock gets hit; one of the init functions takes the lock and goes to do an expensive hardware init; the other init functions walk the same PCI list and get stuck on the lock as a result. For the common case, we can know there's no chance whatsoever of a match if the device isn't in the drivers ID table... so this patch does that check as a best-effort-avoid-the-lock approach. Bootcharts for before and after can be seen at http://www.fenrus.org/before.svg http://www.fenrus.org/after.svg Note the long time "agp_ali_init" takes in the first graph; my laptop doesn't even have an ALI chip in it! (the bootgraphs look a bit dissimilar, but that's the point, the first one has a bunch of arbitrary delays in it that cause it to look very different) This reduces my kernel boot time by about 20% Signed-off-by: Arjan van de Ven Cc: Alan Stern Signed-off-by: Greg Kroah-Hartman

driver core: replace remaining FUNCTION occurrences

2008-04-20T02:10:29+00:00

__FUNCTION__ is gcc-specific, use __func__ Signed-off-by: Harvey Harrison Signed-off-by: Greg Kroah-Hartman

Driver core: coding style fixes

2008-01-25T06:50:12+00:00

Fix up a number of coding style issues in the drivers/base/ directory that have annoyed me over the years. checkpatch.pl is now very happy. Signed-off-by: Greg Kroah-Hartman

Driver core: fix race in __device_release_driver

2008-01-25T04:40:35+00:00

This patch (as1013) was suggested by David Woodhouse; it fixes a race in the driver core. If a device is unregistered at the same time as its driver is unloaded, the driver's code pages may be unmapped while the remove method is still running. The calls to get_driver() and put_driver() were intended to prevent this, but they don't work if the driver's module count has already dropped to 0. Instead, the patch keeps the device on the driver's list until after the remove method has returned. This forces the necessary synchronization to occur. Signed-off-by: Alan Stern Signed-off-by: David Woodhouse Signed-off-by: Greg Kroah-Hartman

Driver core: clean up debugging messages

2008-01-25T04:40:35+00:00

The driver core debugging messages are a mess. This provides a unified message that makes them actually useful. The format for new kobject debug messages should be: driver/bus/class: 'OBJECT_NAME': FUNCTION_NAME: message.\n Note, the class code is not changed in this patch due to pending patches in my queue that this would conflict with. A later patch will clean them up. Cc: Kay Sievers Signed-off-by: Greg Kroah-Hartman

Driver core: move the static kobject out of struct driver

2008-01-25T04:40:35+00:00

This patch removes the kobject, and a few other driver-core-only fields out of struct driver and into the driver core only. Now drivers can be safely create on the stack or statically (like they currently are.) Cc: Kay Sievers Signed-off-by: Greg Kroah-Hartman

driver core: remove fields from struct bus_type

2008-01-25T04:40:33+00:00

struct bus_type is static everywhere in the kernel. This moves the kobject in the structure out of it, and a bunch of other private only to the driver core fields are now moved to a private structure. This lets us dynamically create the backing kobject properly and gives us the chance to be able to document to users exactly how to use the struct bus_type as there are no fields they can improperly access. Thanks to Kay for the build fixes on this patch. Cc: Kay Sievers Signed-off-by: Greg Kroah-Hartman

driver core: fix kernel doc of device_release_driver

2007-07-11T23:09:02+00:00

Signed-off-by: Stefan Richter Signed-off-by: Greg Kroah-Hartman

driver core: properly get driver in device_release_driver

2007-07-11T23:09:01+00:00

Signed-off-by: Stefan Richter Signed-off-by: Greg Kroah-Hartman

Driver core: kill unused code

2007-06-08T19:41:07+00:00

CC drivers/base/dd.o drivers/base/dd.c:211: warning: =E2=80=98device_probe_drivers=E2=80=99 defi= ned but not used Looks like the following is dead. Signed-off-by: Stephen Hemminger Signed-off-by: Greg Kroah-Hartman

kernel/linux.git/drivers/base/dd.c, branch linux-2.6.28.y

device model: Do a quickcheck for driver binding before doing an expensive check

driver core: replace remaining __FUNCTION__ occurrences

Driver core: coding style fixes

Driver core: fix race in __device_release_driver

Driver core: clean up debugging messages

Driver core: move the static kobject out of struct driver

driver core: remove fields from struct bus_type

driver core: fix kernel doc of device_release_driver

driver core: properly get driver in device_release_driver

Driver core: kill unused code

driver core: replace remaining FUNCTION occurrences