linux-stable.git/drivers/base/base.h, branch linux-2.6.31.y

Driver core: add new device to bus's list before probing

2009-10-05T16:32:33+00:00

commit 2023c610dc54a4f4130b0494309a9bd668ca3df8 upstream.

This patch (as1271) affects when new devices get linked into their
bus's list of devices.  Currently this happens after probing, and it
doesn't happen at all if probing fails.  Clearly this is wrong,
because at that point quite a few symbolic links have already been
created in sysfs.  We are committed to adding the device, so it should
be linked into the bus's list regardless.

In addition, this needs to happen before the uevent announcing the new
device gets issued.  Otherwise user programs might try to access the
device before it has been added to the bus.

To fix both these problems, the patch moves the call to
klist_add_tail() forward from bus_attach_device() to bus_add_device().
Since bus_attach_device() now does nothing but probe for drivers, it
has been renamed to bus_probe_device().  And lastly, the kerneldoc is
updated.

Signed-off-by: Alan Stern 
CC: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman

driver core: fix driver_match_device

2009-04-16T23:17:09+00:00

This patch fixes a bug introduced in commit
49b420a13ff95b449947181190b08367348e3e1b.

If a instance of bus_type doesn't have  .match method,
all .probe of drivers in the bus should be called, or else
the .probe have not a chance to be called.

Signed-off-by: Ming Lei 
Reported-by: Guennadi Liakhovetski 
Signed-off-by: Greg Kroah-Hartman

driver core: move knode_bus into private structure

2009-03-24T23:38:25+00:00

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

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

driver core: move knode_driver into private structure

2009-03-24T23:38:25+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: move klist_children into private structure

2009-03-24T23:38:25+00:00

Nothing outside of the driver core should ever touch klist_children, or
knode_parent, so move them out of the public eye.

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

driver core: create a private portion of struct device

2009-03-24T23:38:25+00:00

This is to be used to move things out of struct device that no code
outside of the driver core should ever touch.

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

driver core: check bus->match without holding device lock

2009-03-24T23:38:24+00:00

This patch moves bus->match out from driver_probe_device and
does not hold device lock to check the match between a device
and a driver.

The idea has been verified by the commit 6cd495860901,
which leads to a faster boot. But the commit 6cd495860901 has
the following drawbacks: 1),only does the quick check in
the path of __driver_attach->driver_probe_device, not in other
paths; 2),for a matched device and driver, check the same match
twice. It is a waste of cpu ,especially for some drivers with long
device id table (eg. usb-storage driver).

This patch adds a helper of driver_match_device to check the match
in all paths, and testes the match only once.

Signed-off-by: Ming Lei 
Acked-by: Cornelia Huck 
Signed-off-by: Greg Kroah-Hartman

PM: Split up sysdev_[suspend|resume] from device_power_[down|up]

2009-02-22T18:33:44+00:00

Move the sysdev_suspend/resume from the callee to the callers, with
no real change in semantics, so that we can rework the disabling of
interrupts during suspend/hibernation.

This is based on an earlier patch from Linus.

Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Linus Torvalds

Revert "driver core: create a private portion of struct device"

2009-01-09T23:06:12+00:00

This reverts commit 2831fe6f9cc4e16c103504ee09a47a084297c0f3.

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

Revert "driver core: move klist_children into private structure"

2009-01-09T22:55:37+00:00

This reverts commit 11c3b5c3e08f4d855cbef52883c266b9ab9df879.

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