- 24 Mar, 2009 40 commits
-
-
Dave Young authored
If the bus_type is not registerd, driver_register to that bus will cause oops. I found this bug when test built-in usb serial drivers (ie. aircable driver) with 'nousb' cmdline params. In this patch: 1. set the bus->p=NULL when bus_register failed and unregisterd. 2. if bus->p is NULL, driver_register BUG_ON will be triggered. Signed-off-by:
Dave Young <hidave.darkstar@gmail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Geert Uytterhoeven authored
The patch from Ming Lei <tom.leiming@gmail.com> entitled: platform driver: fix incorrect use of 'platform_bus_type' with 'struct devic introduced the following warnings on m68k, as `dev' is now a `struct platform_device *' instead of a `struct device *': | drivers/scsi/a4000t.c:64: warning: passing argument 3 of 'NCR_700_detect' from incompatible pointer type | drivers/scsi/mvme16x_scsi.c:67: warning: passing argument 3 of 'NCR_700_detect' from incompatible pointer type | drivers/scsi/bvme6000_scsi.c:61: warning: passing argument 3 of 'NCR_700_detect' from incompatible pointer type I think the below is missing (untested on real hardware). Signed-off-by:Geert Uytterhoeven <geert@linux-m68k.org> Cc: Ming Lei <tom.leiming@gmail.com> Signed-off-by:
-
Ming Lei authored
This patch fixes the bug reported in http://bugzilla.kernel.org/show_bug.cgi?id=11681. "Lots of device drivers register a 'struct device_driver' with the '.bus' member set to '&platform_bus_type'. This is wrong, since the platform_bus functions expect the 'struct device_driver' to be wrapped up in a 'struct platform_driver' which provides some additional callbacks (like suspend_late, resume_early). The effect may be that platform_suspend_late() uses bogus data outside the device_driver struct as a pointer pointer to the device driver's suspend_late() function or other hard to reproduce failures."(Lothar Wassmann) Signed-off-by:
Ming Lei <tom.leiming@gmail.com> Acked-by:
Henrique de Moraes Holschuh <hmh@hmh.eng.br> Acked-by:
David Brownell <dbrownell@users.sourceforge.net> Signed-off-by:
-
Ian Abbott authored
If a UIO memory region does not start on a page boundary but straddles one, the number of actual pages that overlap the memory region may be calculated incorrectly because the offset isn't taken into account. If userspace sets the mmap length to offset+size, it may fail with -EINVAL if UIO thinks it's trying to allocate too many pages. Signed-off-by:
Ian Abbott <abbotti@mev.co.uk> Cc: Hans J. Koch <hjk@linutronix.de> Signed-off-by:
-
Brandon Philips authored
UIO driver for the Adrienne Electronics Corporation PCI time code device. This device differs from other UIO devices since it uses I/O ports instead of memory mapped I/O. In order to make it possible for UIO to work with this device a utility, uioport, can be used to read and write the ports. uioport is designed to be a setuid program and checks the permissions of the /dev/uio* node and if the user has write permissions it will use iopl and out*/in* to access the device. [1] git clone git://ifup.org/philips/uioport.gitSigned-off-by:
Brandon Philips <brandon@ifup.org> Signed-off-by:
Hans J. Koch <hjk@linutronix.de> Signed-off-by:
-
Hans J. Koch authored
If a UIO device has several memory mappings, it can be difficult for userspace to find the right one. The situation becomes even worse if the UIO driver can handle different versions of a card that have different numbers of mappings. Benedikt Spranger has such cards and pointed this out to me. Thanks, Bene! To address this problem, this patch adds "name" sysfs attributes for each mapping. Userspace can use these to clearly identify each mapping. The name string is optional. If a driver doesn't set it, an empty string will be returned, so this patch won't break existing drivers. The same problem exists for port region information, so a "name" attribute is added there, too. Signed-off-by:
-
Eric Miao authored
Now platform_device is being widely used on SoC processors where the peripherals are attached to the system bus, which is simple enough. However, silicon IPs for these SoCs are usually shared heavily across a family of processors, even products from different companies. This makes the original simple driver name based matching insufficient, or simply not straight-forward. Introduce a module id table for platform devices, and makes it clear that a platform driver is able to support some shared IP and handle slight differences across different platforms (by 'driver_data'). Module alias is handled automatically when a MODULE_DEVICE_TABLE() is defined. To not disturb the current platform drivers too much, the matched id entry is recorded and can be retrieved by platform_get_device_id(). Signed-off-by:
Eric Miao <eric.miao@marvell.com> Cc: Kay Sievers <kay.sievers@vrfy.org> Cc: Ben Dooks <ben-linux@fluff.org> Signed-off-by:
-
Eric Miao authored
This helps the code look more consistent and cleaner. Signed-off-by:
-
Ming Lei authored
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 6cd49586, which leads to a faster boot. But the commit 6cd49586 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:
Cornelia Huck <cornelia.huck@de.ibm.com> Signed-off-by:
-
Eric W. Biederman authored
sysfs_get_inode ultimately calls sysfs_count_nlink when the a directory inode is fectched. sysfs_count_nlink needs to be called under the sysfs_mutex to guard against the unlikely but possible scenario that the root directory is changing as we are counting the number entries in it, and just in general to be consistent. Signed-off-by:
Eric W. Biederman <ebiederm@aristanetworks.com> Acked-by:
Tejun Heo <tj@kernel.org> Signed-off-by:
-
Qinghuang Feng authored
SYSFS_MAGIC has been added into magic.h, so only use that definition in magic.h to avoid potential consistency problem. Signed-off-by:
Qinghuang Feng <qhfeng.kernel@gmail.com> Signed-off-by:
-
Kay Sievers authored
Now that all users of bus_id is gone, we can remove it from struct device. Signed-off-by:
Kay Sievers <kay.sievers@vrfy.org> Signed-off-by:
-
Sachin Sant authored
Replace references to bus_id with dev_name() to fix fhci driver build break. drivers/usb/host/fhci-hcd.c:586: error: struct device has no member named bus_id drivers/usb/host/fhci-hcd.c:653: error: struct device has no member named bus_id drivers/usb/host/fhci-dbg.c:111: error: struct device has no member named bus_id Signed-off-by:
Sachin Sant <sachinp@in.ibm.com> Acked-by:
Anton Vorontsov <avorontsov@ru.mvista.com> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by:
-
Greg Kroah-Hartman authored
These simple debug statments should be using dev_dbg() instead of accessing bus_id directly (or they should use device_name). As bus_id is going away, this patch is necessary. Acked-by:
Geoff Levand <geoffrey.levand@am.sony.com> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Cc: inaky.perez-gonzalez@intel.com Cc: linux-wimax@intel.com Acked-by:
-
Kay Sievers authored
Cc: sameo@openedhand.com Acked-by:
-
Kay Sievers authored
Cc: James.Bottomley@HansenPartnership.com Acked-by:
-
Kay Sievers authored
Cc: Michael Buesch <mb@bu3sch.de> Acked-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Cc: Dan Williams <dan.j.williams@intel.com> Acked-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Cc: mchehab@infradead.org Cc: linux-media@vger.kernel.org Acked-by:
-
Kay Sievers authored
Cc: airlied@linux.ie Acked-by:
-
Kay Sievers authored
Cc: davem@davemloft.net Cc: netdev@vger.kernel.org Acked-by:
-
Kay Sievers authored
Cc: a.zummo@towertech.it Cc: rtc-linux@googlegroups.com Signed-off-by:
Alessandro Zummo <a.zummo@towertech.it> Signed-off-by:
-
Kay Sievers authored
Cc: Dominik Brodowski <linux@dominikbrodowski.net> Cc: linux-pcmcia@lists.infradead.org Acked-by:
-
Kay Sievers authored
Cc: macro@linux-mips.org Acked-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Cc: davem@davemloft.net Acked-by:
-
Kay Sievers authored
Cc: schwidefsky@de.ibm.com Cc: linux-s390@vger.kernel.org Acked-by:
-
Kay Sievers authored
Cc: mporter@kernel.crashing.org Acked-by:
-
Kay Sievers authored
Cc: jbarnes@virtuousgeek.org Cc: linux-pci@vger.kernel.org Acked-by:
-
Kay Sievers authored
Cc: dwmw2@infradead.org Cc: linux-mtd@lists.infradead.org Acked-by:
-
Kay Sievers authored
Cc: drzeus-mmc@drzeus.cx Acked-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Acked-by:
-
Kay Sievers authored
Cc: dbrownell@users.sourceforge.net Cc: spi-devel-general@lists.sourceforge.net Acked-by:
-
Kay Sievers authored
Cc: dougthompson@xmission.com Cc: bluesmoke-devel@lists.sourceforge.net Acked-by:
-
