Linux kernel stable tree https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=linux-2.6.21.y 2007-03-06T17:30:24+00:00 2007-03-06T17:30:24+00:00 Dave Jones davej@redhat.com 2007-03-06T09:42:00+00:00 urn:sha1:b9860ecf2553fbc4c3bd66f5df7e82a6d5179775 drivers/video/nvidia/nv_backlight.c: In function 'nvidia_bl_init': drivers/video/nvidia/nv_backlight.c:103: error: implicit declaration of function 'pmac_has_backlight_type' Signed-off-by: Dave Jones <davej@redhat.com> Signed-off-by: Antonino Daplas <adaplas@gmail.com> Cc: James Simmons <jsimmons@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> 2007-03-05T08:49:38+00:00 Richard Purdie rpurdie@rpsys.net 2007-03-03T17:43:52+00:00 urn:sha1:202d4e602555e68c2bc71775228876b0356785c8 Enabling the backlight by default appears to cause problems for many users. This patch disables backlight controls unless explicitly enabled by users via a module parameter. Since PMAC users are known to work, default to enabled in that case. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-03-05T08:49:38+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-26T22:06:09+00:00 urn:sha1:238576e12fef1d52751c6e08db2d0bdb0e248caf Fix a mix up when the nvidia driver was converted resulting in the backlight having an incorrect initial brightness. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-20T09:26:53+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-10T23:07:48+00:00 urn:sha1:599a52d12629394236d785615808845823875868 Per device data such as brightness belongs to the indivdual device and should therefore be separate from the the backlight operation function pointers. This patch splits the two types of data and allows simplifcation of some code. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-20T09:26:40+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-10T15:04:08+00:00 urn:sha1:321709c5994f952b78d567fd7083dbebbdc381b7 Move the setting/unsetting of pmac_backlight into the backlight core instead of doing it in each driver. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-20T08:38:46+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-10T14:10:33+00:00 urn:sha1:37ce69a57ff217a4ca0871e9ee5aa58c052b7d86 fb_info->bl_mutex is badly thought out and the backlight class doesn't need it if the framebuffer/backlight register/unregister order is consistent, particularly after the backlight locking fixes. Fix the drivers to use the order: backlight_device_register() register_framebuffer() unregister_framebuffer() backlight_device_unregister() and turn bl_mutex into a lock for the bl_curve data only. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-20T08:38:45+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-09T00:34:52+00:00 urn:sha1:1cfc97f21f6ab91df8d5617fcbf758322fdd238b nvidia_bl_set_power isn't needed since the backlight class handles this by receiving fb events itself and calling update_status so remove it. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-20T08:38:45+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-08T22:25:09+00:00 urn:sha1:28ee086d5b36aab2931f6740e409bb0fb6c65e5f backlight_device->sem has a very specific use as documented in the header file. The external users of this are using it for a different reason, to serialise access to the update_status() method. backlight users were supposed to implement their own internal serialisation of update_status() if needed but everyone is doing things differently and incorrectly. Therefore add a global mutex to take care of serialisation for everyone, once and for all. Locking for get_brightness remains optional since most users don't need it. Also update the lcd class in a similar way. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-20T08:37:40+00:00 Richard Purdie rpurdie@rpsys.net 2007-02-08T00:06:32+00:00 urn:sha1:dfcba200679dc3f62212154b65b40b835ce69ab7 Remove uneeded owner field from backlight_properties structure. Nothing uses it and it is unlikely that it will ever be used. The backlight class uses other means to ensure that nothing references unloaded code. Based on a patch from Dmitry Torokhov <dtor@insightbb.com> Signed-off-by: Richard Purdie <rpurdie@rpsys.net> 2007-02-14T16:09:54+00:00 Tim Schmielau tim@physik3.uni-rostock.de 2007-02-14T08:33:14+00:00 urn:sha1:cd354f1ae75e6466a7e31b727faede57a1f89ca5 After Al Viro (finally) succeeded in removing the sched.h #include in module.h recently, it makes sense again to remove other superfluous sched.h includes. There are quite a lot of files which include it but don't actually need anything defined in there. Presumably these includes were once needed for macros that used to live in sched.h, but moved to other header files in the course of cleaning it up. To ease the pain, this time I did not fiddle with any header files and only removed #includes from .c-files, which tend to cause less trouble. Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha, arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig, allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all configs in arch/arm/configs on arm. I also checked that no new warnings were introduced by the patch (actually, some warnings are removed that were emitted by unnecessarily included header files). Signed-off-by: Tim Schmielau <tim@physik3.uni-rostock.de> Acked-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>