Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.35.y 2010-05-21T16:37:31+00:00 2010-05-21T16:37:31+00:00 Chris Wright chrisw@sous-sol.org 2010-05-13T01:28:57+00:00 urn:sha1:2c3c8bea608866d8bd9dcf92657d57fdcac011c5 This allows bin_attr->read,write,mmap callbacks to check file specific data (such as inode owner) as part of any privilege validation. Signed-off-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-05-20T20:21:37+00:00 Alan Stern stern@rowland.harvard.edu 2010-04-02T17:22:16+00:00 urn:sha1:a90309860b0935805d49e75499fb8dc59fea8e94 This patch (as1367) deprecates USB's power/level sysfs attribute in favor of the power/control attribute provided by the runtime PM core. The two attributes do the same thing. It would be nice to replace power/level with a symlink to power/control, but at the moment sysfs doesn't offer any way to do so. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-05-20T20:21:37+00:00 Alan Stern stern@rowland.harvard.edu 2010-04-02T17:22:09+00:00 urn:sha1:9e18c821659d836bd63f88df3c19729327728496 This patch (as1366) replaces the private routines usb_enable_autosuspend() and usb_disable_autosuspend() with calls to the standard pm_runtime_allow() and pm_runtime_forbid() functions in the runtime PM framework. They do the same thing. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-03-02T22:54:11+00:00 Alan Stern stern@rowland.harvard.edu 2010-01-08T17:57:02+00:00 urn:sha1:5899f1e020c8d53b2b6fbd6a6cf39c891ccdfade This patch (as1327) changes the way negative autosuspend delays prevent device from autosuspending. The current code checks for negative values explicitly in the autosuspend_check() routine. The updated code keeps things from getting that far by using usb_autoresume_device() to increment the usage counter when a negative delay is set, and by using usb_autosuspend_device() to decrement the usage counter when a non-negative delay is set. This complicates the set_autosuspend() attribute method code slightly, but it will reduce the overall power management overhead. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-03-02T22:54:10+00:00 Alan Stern stern@rowland.harvard.edu 2010-01-08T17:56:54+00:00 urn:sha1:088f7fec8a0e683db72fd8826c5d3ab914e197b1 This patch (as1326) adds usb_enable_autosuspend() and usb_disable_autosuspend() routines for use by drivers. If a driver knows that its device can handle suspends and resumes correctly, it can enable autosuspend all by itself. This is equivalent to the user writing "auto" to the device's power/level attribute. The implementation differs slightly from what it used to be. Now autosuspend is disabled simply by doing usb_autoresume_device() (to increment the usage counter) and enabled by doing usb_autosuspend_device() (to decrement the usage counter). The set_level() attribute method is updated to use the new routines, and the USB Power-Management documentation is updated. The patch adds a usb_enable_autosuspend() call to the hub driver's probe routine, allowing the special-case code for hubs in quirks.c to be removed. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-03-02T22:54:08+00:00 Alan Stern stern@rowland.harvard.edu 2010-01-08T17:56:42+00:00 urn:sha1:0c4db6df915bc470f0cd32fe48287fa6eb6adfb4 This patch (as1325) changes the locking for the persist_enabled flag in struct usb_device. Now it is protected by the device lock, along with all its neighboring bit flags, instead of the PM lock (which is about to vanish anyway). Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-03-02T22:54:08+00:00 Alan Stern stern@rowland.harvard.edu 2010-01-08T17:56:19+00:00 urn:sha1:62e299e61a6ffe8131fa85a984c3058b68586f5d This patch (as1323) changes the locking requirements for usb_autosuspend_device(), usb_autoresume_device(), and usb_try_autosuspend_device(). This isn't a very important change; mainly it's meant to make the locking more uniform. The most tricky part of the patch involves changes to usbdev_open(). To avoid an ABBA locking problem, it was necessary to reduce the region protected by usbfs_mutex. Since that mutex now protects only against simultaneous open and remove, this posed no difficulty -- its scope was larger than necessary. And it turns out that usbfs_mutex is no longer needed in usbdev_release() at all. The list of usbfs "ps" structures is now protected by the device lock instead of by usbfs_mutex. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-03-02T22:53:36+00:00 Greg Kroah-Hartman gregkh@suse.de 2010-01-14T19:08:04+00:00 urn:sha1:551cdbbeb118bd5ed301f8749aef69219284399b It's really the wireless speed, so rename the thing to make more sense. Based on a recommendation from David Vrabel Cc: David Vrabel <david.vrabel@csr.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-03-02T22:53:23+00:00 Oliver Neukum oliver@neukum.org 2010-01-16T00:33:03+00:00 urn:sha1:ef955341f692475236f0fbe6853f49337dff77a5 Some devices which use mode switching revert to their primary mode as they are reset. They must not be reset for error handling. As user spaces makes the switch it also has to tell the kernel that a device is quirky. Signed-off-by: Oliver Neukum <oliver@neukum.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2010-01-20T23:24:35+00:00 Greg Kroah-Hartman gregkh@suse.de 2010-01-14T18:33:19+00:00 urn:sha1:b132b04e193908a94d95065d0628f8fb0159cc55 These controllers say "unknown" for their speed in sysfs, which obviously isn't correct. Reported-by: Kurt Garloff <garloff@novell.com> Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com> Cc: David Vrabel <david.vrabel@csr.com> Cc: stable <stable@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>