linux-toradex.git/drivers/base/core.c, branch v2.6.16-rc5

[PATCH] DocBook: fix kernel-doc comments

2006-01-10T16:01:53+00:00

Fix typos in comments to remove kernel-doc warnings.

Signed-off-by: Martin Waitz 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] driver core: replace "hotplug" by "uevent"

2006-01-05T00:18:08+00:00

Leave the overloaded "hotplug" word to susbsystems which are handling
real devices. The driver core does not "plug" anything, it just exports
the state to userspace and generates events.

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

[PATCH] kernel-doc: drivers/base fixes

2005-10-28T16:52:56+00:00

driver/base: add missing function parameters; eliminate all warnings.

Signed-off-by: Randy Dunlap 
Signed-off-by: Greg Kroah-Hartman

[PATCH] add sysfs attr to re-emit device hotplug event

2005-10-28T16:52:51+00:00

A "coldplug + udevstart" can be simple like this:
  for i in /sys/block/*/*/uevent; do echo 1 > $i; done
  for i in /sys/class/*/*/uevent; do echo 1 > $i; done
  for i in /sys/bus/*/devices/*/uevent; do echo 1 > $i; done

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

[PATCH] driver model wakeup flags

2005-10-28T16:52:50+00:00

This is a refresh of an earlier patch to add "wakeup" support to the
PM core model.  This provides per-device bus-neutral control of the
use of wakeup events.

  * "struct device_pm_info" has two bits that are initialized as
    part of setting up the enclosing struct device:
      - "can_wakeup", reflecting hardware capabilities
      - "may_wakeup", the policy setting (when CONFIG_PM)

  * There's a writeable sysfs "wakeup" file, with one of two values:
      - "enabled", when the policy is to allow wakeup
      - "disabled", when the policy is not to allow it
      - "" if the device can't currently issue wakeups

By default, wakeup is enabled on all devices that support it.  If its
driver doesn't support it ... treat it as a bug.  :)

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

[PATCH] fix klist semantics for lists which have elements removed on traversal

2005-09-08T01:26:54+00:00

The problem is that klists claim to provide semantics for safe traversal of
lists which are being modified.  The failure case is when traversal of a
list causes element removal (a fairly common case).  The issue is that
although the list node is refcounted, if it is embedded in an object (which
is universally the case), then the object will be freed regardless of the
klist refcount leading to slab corruption because the klist iterator refers
to the prior element to get the next.

The solution is to make the klist take and release references to the
embedding object meaning that the embedding object won't be released until
the list relinquishes the reference to it.

(akpm: fast-track this because it's needed for the 2.6.13 scsi merge)

Signed-off-by: James Bottomley 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] klist: fix klist to have the same klist_add semantics as list_head

2005-09-05T23:03:13+00:00

at the moment, the list_head semantics are

list_add(node, head)

whereas current klist semantics are

klist_add(head, node)

This is bound to cause confusion, and since klist is the newcomer, it
should follow the list_head semantics.

I also added missing include guards to klist.h

Signed-off-by: James Bottomley 
Signed-off-by: Greg Kroah-Hartman

[PATCH] Driver core: Use klist_del() instead of klist_remove().

2005-06-30T05:48:05+00:00

Use klist_del() instead of klist_remove() when unregistering devices.
This will prevent a deadlock when executing a recursive unregister using
device_for_each_child().

Signed-off-by Patrick Mochel 
Signed-off-by: Greg Kroah-Hartman

[PATCH] Driver core: change device_attribute callbacks

2005-06-20T22:15:31+00:00

This patch adds the device_attribute paramerter to the
device_attribute store and show sysfs callback functions, and passes a
reference to the attribute when the callbacks are called.

Signed-off-by: Yani Ioannou 
Signed-off-by: Greg Kroah-Hartman

[PATCH] Use a klist for device child lists.

2005-06-20T22:15:23+00:00

- Use klist iterator in device_for_each_child(), making it safe to use for
  removing devices.
- Remove unused list_to_dev() function.
- Kills all usage of devices_subsys.rwsem.

Signed-off-by: Patrick Mochel 
Signed-off-by: Greg Kroah-Hartman