linux-toradex.git/drivers/base/dd.c, branch tegra-9.12.11

Consolidate driver_probe_done() loops into one place

2009-02-21T22:17:17+00:00

there's a few places that currently loop over driver_probe_done(), and
I'm about to add another one. This patch abstracts it into a helper
to reduce duplication.

Signed-off-by: Arjan van de Ven 
Signed-off-by: Rafael J. Wysocki 
Cc: Len Brown 
Acked-by: Greg KH 
Signed-off-by: Linus Torvalds

Revert "driver core: move knode_driver into private structure"

2009-01-09T22:44:18+00:00

This reverts commit 93e746db183b3bdbbda67900f79b5835f9cb388f.

Turns out that device_initialize shouldn't fail silently.
This series needs to be reworked in order to get into proper
shape.

Reported-by: Stefan Richter 
Cc: Alan Cox 
Cc: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman

driver core:fix duplicate removing driver link in __device_release_driver

2009-01-06T18:44:33+00:00

In __device_release_driver(),driver_sysfs_remove() has removed the
driver link under device dir in sysfs, but sysfs_remove_link() is
called again to do such thing. Remove the duplicate call to
sys_remove_link().

Signed-off-by: Ming Lei 
Signed-off-by: Greg Kroah-Hartman

driver core: move knode_driver into private structure

2009-01-06T18:44:32+00:00

Nothing outside of the driver core should ever touch knode_driver, so
move it out of the public eye.

Cc: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman

driver core: struct device - replace bus_id with dev_name(), dev_set_name()

2009-01-06T18:44:31+00:00

Signed-off-by: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman

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