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

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

PCI: remove the broken PCI_MULTITHREAD_PROBE option

2007-05-03T02:02:38+00:00

This patch removes the PCI_MULTITHREAD_PROBE option that had already 
been marked as broken.

Signed-off-by: Adrian Bunk 
Signed-off-by: Greg Kroah-Hartman

driver core: don't fail attaching the device if it cannot be bound

2007-04-27T17:57:29+00:00

Don't fail bus_attach_device() if the device cannot be bound.

If dev->driver has been specified, reset it to NULL if device_bind_driver()
failed and add the device as an unbound device.  As a result,
bus_attach_device() now cannot fail, and we can remove some checking from
device_add().

Also remove an unneeded check in bus_rescan_devices_helper().

Signed-off-by: Cornelia Huck 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

driver core: per-subsystem multithreaded probing

2007-04-27T17:57:28+00:00

Make multithreaded probing work per subsystem instead of per driver.

It doesn't make much sense to probe the same device for multiple drivers in
parallel (after all, only one driver can bind to the device).  Instead, create
a probing thread for each device that probes the drivers one after another. 
Also make the decision to use multi-threaded probe per bus instead of per
device and adapt the pci code.

Signed-off-by: Cornelia Huck 
Cc: Benjamin Herrenschmidt 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

devres: device resource management

2007-02-09T22:39:36+00:00

Implement device resource management, in short, devres.  A device
driver can allocate arbirary size of devres data which is associated
with a release function.  On driver detach, release function is
invoked on the devres data, then, devres data is freed.

devreses are typed by associated release functions.  Some devreses are
better represented by single instance of the type while others need
multiple instances sharing the same release function.  Both usages are
supported.

devreses can be grouped using devres group such that a device driver
can easily release acquired resources halfway through initialization
or selectively release resources (e.g. resources for port 1 out of 4
ports).

This patch adds devres core including documentation and the following
managed interfaces.

* alloc/free	: devm_kzalloc(), devm_kzfree()
* IO region	: devm_request_region(), devm_release_region()
* IRQ		: devm_request_irq(), devm_free_irq()
* DMA		: dmam_alloc_coherent(), dmam_free_coherent(),
		  dmam_declare_coherent_memory(), dmam_pool_create(),
		  dmam_pool_destroy()
* PCI		: pcim_enable_device(), pcim_pin_device(), pci_is_managed()
* iomap		: devm_ioport_map(), devm_ioport_unmap(), devm_ioremap(),
		  devm_ioremap_nocache(), devm_iounmap(), pcim_iomap_table(),
		  pcim_iomap(), pcim_iounmap()

Signed-off-by: Tejun Heo 
Signed-off-by: Jeff Garzik

driver core: Change function call order in device_bind_driver().

2007-02-07T18:37:13+00:00

Change function call order in device_bind_driver().

If we create symlinks (which might fail) before adding the device to the list
we don't have to clean up afterwards (which we didn't).

Signed-off-by: Cornelia Huck 
Signed-off-by: Greg Kroah-Hartman

driver core: Don't stop probing on ->probe errors.

2007-02-07T18:37:12+00:00

Don't stop on the first ->probe error that is not -ENODEV/-ENXIO.

There might be a driver registered returning an unresonable return code, and
this stops probing completely even though it may make sense to try the next
possible driver. At worst, we may end up with an unbound device.

Signed-off-by: Cornelia Huck 
Signed-off-by: Greg Kroah-Hartman

Driver core: fix "driver" symlink timing

2006-12-01T22:51:58+00:00

Create the "driver" link before the child device may be created by
the probing logic. This makes it possible for userspace (udev), to
determine the driver property of the parent device, at the time the
child device is created.

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