linux-toradex.git/drivers/base/dd.c, branch v2.6.39-rc2

Driver core: Add BUS_NOTIFY_BIND_DRIVER

2010-08-05T20:53:35+00:00

Add BUS_NOTIFY_BIND_DRIVER as a bus notifier event.

For driver binding/unbinding we with this in
place have the following bus notifier events:
 - BUS_NOTIFY_BIND_DRIVER - before ->probe()
 - BUS_NOTIFY_BOUND_DRIVER - after ->probe()
 - BUS_NOTIFY_UNBIND_DRIVER - before ->remove()
 - BUS_NOTIFY_UNBOUND_DRIVER - after ->remove()

The event BUS_NOTIFY_BIND_DRIVER allows bus code
to be notified that ->probe() is about to be called.

Useful for bus code that needs to setup hardware before
the driver gets to run. With this in place platform
drivers can be loaded and unloaded as modules and the
new BIND event allows bus code to control for instance
device clocks that must be enabled before the driver
can be executed.

Without this patch there is no way for the bus code to
get notified that a modular driver is about to be probed.

Signed-off-by: Magnus Damm 
Signed-off-by: Greg Kroah-Hartman

driver-core: fix potential race condition in drivers/base/dd.c

2010-05-21T16:37:29+00:00

This patch fix a potential race condition in the driver_bound() function
in the file driver/base/dd.c.

The broadcast of the BUS_NOTIFY_BOUND_DRIVER notifier should be done
after adding the new device to the driver list. Otherwise notifier
listener will fail if they use functions like usb_find_interface().

The patch is against kernel 2.6.33. Please merge it.

Signed-off-by: Stefani Seibold 
Signed-off-by: Greg Kroah-Hartman

Driver core: create lock/unlock functions for struct device

2010-03-08T01:04:52+00:00

In the future, we are going to be changing the lock type for struct
device (once we get the lockdep infrastructure properly worked out)  To
make that changeover easier, and to possibly burry the lock in a
different part of struct device, let's create some functions to lock and
unlock a device so that no out-of-core code needs to be changed in the
future.

This patch creates the device_lock/unlock/trylock() functions, and
converts all in-tree users to them.

Cc: Thomas Gleixner 
Cc: Jean Delvare 
Cc: Dave Young 
Cc: Ming Lei 
Cc: Jiri Kosina 
Cc: Phil Carmody 
Cc: Arjan van de Ven 
Cc: Cornelia Huck 
Cc: Rafael J. Wysocki 
Cc: Pavel Machek 
Cc: Len Brown 
Cc: Magnus Damm 
Cc: Alan Stern 
Cc: Randy Dunlap 
Cc: Stefan Richter 
Cc: David Brownell 
Cc: Vegard Nossum 
Cc: Jesse Barnes 
Cc: Alex Chiang 
Cc: Kenji Kaneshige 
Cc: Andrew Morton 
Cc: Andrew Patterson 
Cc: Yu Zhao 
Cc: Dominik Brodowski 
Cc: Samuel Ortiz 
Cc: Wolfram Sang 
Cc: CHENG Renquan 
Cc: Oliver Neukum 
Cc: Frans Pop 
Cc: David Vrabel 
Cc: Kay Sievers 
Cc: Sarah Sharp 
Signed-off-by: Greg Kroah-Hartman

tree-wide: fix assorted typos all over the place

2009-12-04T14:39:55+00:00

That is "success", "unknown", "through", "performance", "[re|un]mapping"
, "access", "default", "reasonable", "[con]currently", "temperature"
, "channel", "[un]used", "application", "example","hierarchy", "therefore"
, "[over|under]flow", "contiguous", "threshold", "enough" and others.

Signed-off-by: André Goddard Rosa 
Signed-off-by: Jiri Kosina

Driver core: move dev_get/set_drvdata to drivers/base/dd.c

2009-09-15T16:50:47+00:00

No one should directly access the driver_data field, so remove the field
and make it private.  We dynamically create the private field now if it
is needed, to handle drivers that call get/set before they are
registered with the driver core.

Also update the copyright notices on these files while we are there.

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

PM: Introduce core framework for run-time PM of I/O devices (rev. 17)

2009-08-22T22:04:44+00:00

Introduce a core framework for run-time power management of I/O
devices.  Add device run-time PM fields to 'struct dev_pm_info'
and device run-time PM callbacks to 'struct dev_pm_ops'.  Introduce
a run-time PM workqueue and define some device run-time PM helper
functions at the core level.  Document all these things.

Special thanks to Alan Stern for his help with the design and
multiple detailed reviews of the pereceding versions of this patch
and to Magnus Damm for testing feedback.

Signed-off-by: Rafael J. Wysocki 
Acked-by: Magnus Damm

Driver core: fix comment for device_attach()

2009-06-16T04:30:24+00:00

We are looking for matching drivers, not devices.

Signed-off-by: Dmitry Torokhov 
Signed-off-by: Greg Kroah-Hartman

driver core: add BUS_NOTIFY_UNBOUND_DRIVER event

2009-06-16T04:30:24+00:00

This patch adds a new bus notifier event which is emitted _after_ a
device is removed from its driver. This event will be used by the
dma-api debug code to check if a driver has released all dma allocations
for that device.

Signed-off-by: Joerg Roedel 
Signed-off-by: Greg Kroah-Hartman

driver synchronization: make scsi_wait_scan more advanced

2009-04-22T02:40:00+00:00

There is currently only one way for userspace to say "wait for my storage
device to get ready for the modules I just loaded": to load the
scsi_wait_scan module. Expectations of userspace are that once this
module is loaded, all the (storage) devices for which the drivers
were loaded before the module load are present.

Now, there are some issues with the implementation, and the async
stuff got caught in the middle of this: The existing code only
waits for the scsy async probing to finish, but it did not take
into account at all that probing might not have begun yet.
(Russell ran into this problem on his computer and the fix works for him)

This patch fixes this more thoroughly than the previous "fix", which
had some bad side effects (namely, for kernel code that wanted to wait for
the scsi scan it would also do an async sync, which would deadlock if you did
it from async context already.. there's a report about that on lkml):
The patch makes the module first wait for all device driver probes, and then it
will wait for the scsi parallel scan to finish.

Signed-off-by: Arjan van de Ven 
Tested-by: Russell King 
Signed-off-by: Linus Torvalds

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