Tags give the ability to mark specific points in history as being important
-
pm+acpi-3.11-rc5
69fdadfd · ·ACPI and power management fixes for 3.11-rc5 - ACPI-based memory hotplug stopped working after a recent change, because it's not possible to associate sufficiently many "physical" devices with one ACPI device object due to an artificial limit. Fix from Rafael J Wysocki removes that limit and makes memory hotplug work again. - A change made in 3.9 uncovered a bug in the ACPI processor driver preventing NUMA nodes from being put offline due to an ordering issue. Fix from Yasuaki Ishimatsu changes the ordering to make things work again. - One of the recent ACPI video commits (that hasn't been reverted so far) uncovered a bug in the code handling quirky BIOSes that caused some Asus machines to boot with backlight completely off which made it quite difficult to use them afterward. Fix from Felipe Contreras improves the quirk to cover this particular case correctly. - A cpufreq user space interface change made in 3.10 inadvertently renamed the ignore_nice_load sysfs attribute to ignore_nice which resulted in some confusion. Fix from Viresh Kumar changes the name back to ignore_nice_load. - An initialization ordering change made in 3.9 broke cpufreq on loongson2 boards. Fix from Aaro Koskinen restores the correct initialization ordering there. - Fix breakage resulting from a mistake made in 3.9 and causing the detection of some graphics adapters (that were detected correctly before) to fail. There are two objects representing the same PCIe port in the affected systems' ACPI tables and both appear as "enabled" and we are expected to guess which one to use. We used to choose the right one before by pure luck, but when we tried to address another similar corner case, the luck went away. This time we try to make our guessing a bit more educated which is reported to work on those systems. - The /proc/acpi/wakeup interface code is missing some locking which may lead to breakage if that file is written or read during hotplug of wakeup devices. That should be rare but still possible, so it's better to start using the appropriate locking there. /
-
fbdev-fixes-3.11-rc5
70a0f603 · ·fbdev fixes: - omapdss: compilation fix and DVI fix for PandaBoard - mxsfb: fix colors when using 18bit LCD bus
-
regulator-v3.11-rc4
386c90ac · ·regulator: DT binding fixes for v3.11 A couple of fixes to bring the DT binding documentation for Palmas into sync with the code.
-
msm-cleanup3-for-3.12
3294a7e7 · ·General cleanups for MSM for 3.12 This is a series of cleanups to the MSM code. These are a healthy start to bringing the MSM code closer to the state of current ARM code and getting more of it ready for conversion to devicetree.
-
msm-cleanup2-for-3.12
3294a7e7 · ·General cleanups for MSM for 3.12 This is a series of cleanups to the MSM code. These are a healthy start to bringing the MSM code closer to the state of current ARM code and getting more of it ready for conversion to devicetree.
-
iio-for-3.12a
cd6fe065 · ·First round of new IIO drivers, features and cleanups for the 3.12 cycle. There has been a lot of good work going into IIO recently, some of which missed this pull request purely because I haven't caught up with all my emails. Core changes 1) Introduction of devm_iio_device_alloc/free and conversions of lots of drivers (37 + patches so far mostly from Sachin) 2) A Kconfig option to enabled some debug logging subsystem wide. New drivers 1) Nuvoton NAU7802 adc driver 2) Avago APDS9300 ambient light sensor driver. Staging graduations 1) ADIS16260 gyroscope (after a lot fo cleaning up from Lars-Peter) New driver features 1) ST-sensors gain control of which pin is used for dataready. 2) mcp4725 gains eeprom saving (a later fix deals with a wrong return type bug in that patch) 3) A number of drivers have gained module alias' to aid autoloading. Cleanups and minor bug fixes. 1) A number of typos in Kconfig comments 2) Drop remaining mentions of ring buffers (now just buffers) 3) Overrestrictive i2c function checking in the invensense mpu6050 driver 4) Some help text clarifications. 5) store_eeprom is now used in several drivers so move to generic abi docs. 6) Update dac power down options. 7) Add some error handlign to mxs-lradc on stmp_reset_block call. 8) Lars fixed the alphabetical order in various files and added comments to try and prevent them getting messed up again. 9) Dropped some remaining 'reset' attributes for drivers. We have never seen a reason why these should be available. Finally the macro used to define many of these has gone. 10) lps331ap gets an easier to check temperature scale implementation. 11) Various cleanups for the hmc5843 from Peter with a view to getting it ready for a staging graduation. Quite a few other little typo fixes etc. -
iio-fixes-for-3.11b
b1451e54 · ·Second round of IIO fixes for the 3.11 cycle. 1) Fix a long term race in the IIO trigger handling. This only effects cases where a single trigger is in use by multiple devices. 2) ti_am335x fix an issue with incorrect data due to reading before the sequencer is finished.
-
pm+acpi-3.11-rc4
2b44c4db · ·ACPI and power management fixes for 3.11-rc4 - Revert two cpuidle commits added during the 3.8 development cycle that turn out to have introduced a significant performance regression as requested by Jeremy Eder. - The recent patches that made the freezer less heavy-weight introduced a regression causing user-space-driven hibernation using the ioctl() interface to block indefinitely when the hibernate process executes try_to_freeze(). Fix from Colin Cross addresses this by adding a process flag to mark the hibernate/suspend process to inform the freezer that that process should be ignored. - One of the recent cpufreq reverts uncovered a problem in the core causing the cpufreq driver module refcount to become negative after a system suspend-resume cycle. Fix from Rafael J Wysocki. - The evaluation of the ACPI battery _BIX method has never worked correctly, because the commit that added support for it forgot to take the "Revision" field in the return package into account. As a result, the reading of battery info doesn't work at all on some systems, which is addressed by a fix from Lan Tianyu. /
-
vfio-v3.11-rc4
d24cdbfd · ·vfio: misc fixes around overreacting to bus notifier events and a locking fix for a corner case blocked remove.
-
fbdev-fixes-3.11-rc2
7808e329 · ·Small fbdev fixes - Compile fixes - atyfb initialization fix - Fix freeing of the irq in sh7760fb & nuc900fb
-
pinctrl-for-v3.11-2
db6c2c69 · ·Pin control fixes for the v3.11 series: - Driver fixes for AM33xx, SIRF and PFC pin controllers. - Fix a compile warning from the pinctrl single-register driver. - Fix a little nasty memory leak.
-
msm-3.11-fix1
8fd62389 · ·Fixes for MSM for 3.11 Two small fixes for MSM. The first fixes the a gpio controller register address. I didn't see any acks from the devicetree maintainers, so I've copied them on this pull request. The change itself is minor, and just to the register address. The second change removes the gpiomux V1 code from MSM. This was breaking compilation for some of the targets.
-
pm+acpi-3.11-rc3
8e5c2b77 · ·ACPI and power management fixes for 3.11-rc3 - Revert of the ACPI video commit that I hoped would help fix backlight problems related to Windows 8 compatibility on some systems. Unfortunately, it turned out to cause problems to happen too. - Fix for two problems in intel_pstate, a possible failure to respond to a load change on a quiet system and a possible failure to select the highest available P-state on some systems. From Dirk Brandewie. /
-
acpi-video-3.11
efaa14c7 · ·ACPI video support fixes for 3.11 - Change from Aaron Lu makes ACPICA export a variable which can be used by driver code to determine whether or not the BIOS believes that we are compatible with Windows 8. - Change from Matthew Garrett makes the ACPI video driver initialize the ACPI backlight even if it is not going to be used afterward (that is needed for backlight control to work on Thinkpads). - Fix from Rafael J Wysocki implements Windows 8 backlight support workaround making i915 take over bakclight control if the firmware thinks it's dealing with Windows 8. Based on the work of multiple developers including Matthew Garrett, Chun-Yi Lee, Seth Forshee, and Aaron Lu. - Fix from Aaron Lu makes the kernel follow Windows 8 by informing the firmware through the _DOS method that it should not carry out automatic brightness changes, so that brightness can be controlled by GUI. /
-
pm+acpi-3.11-rc2
5a8d2815 · ·Power management and ACPI fixes for 3.11-rc2 - Two cpufreq commits from the 3.10 cycle introduced regressions. The first of them was buggy (it did way much more than it needed to do) and the second one attempted to fix an issue introduced by the first one. Fixes from Srivatsa S Bhat revert both. - If autosleep triggers during system shutdown and the shutdown callbacks of some device drivers have been called already, it may crash the system. Fix from Liu Shuo prevents that from happening by making try_to_suspend() check system_state. - The ACPI memory hotplug driver doesn't clear its driver_data on errors which may cause a NULL poiter dereference to happen later. Fix from Toshi Kani. - The ACPI namespace scanning code should not try to attach scan handlers to device objects that have them already, which may confuse things quite a bit, and it should rescan the whole namespace branch starting at the given node after receiving a bus check notify event even if the device at that particular node has been discovered already. Fixes from Rafael J Wysocki. - New ACPI video blacklist entry for a system whose initial backlight setting from the BIOS doesn't make sense. From Lan Tianyu. - Garbage string output avoindance for ACPI PNP from Liu Shuo. - Two Kconfig fixes for issues introduced recently in the s3c24xx cpufreq driver (when moving the driver to drivers/cpufreq) from Paul Bolle. - Trivial comment fix in pm_wakeup.h from Chanwoo Choi. /
-
iio-fixes-for-3.11a
67dbf54a · ·The first round of IIO fixes for the 3.11 cycle. This set is larger than I would like, partly due to my lack of review time in the weeks before the merge window and partly because a couple of large drivers and the subsystem as a whole seem to be getting a lot more exposure and testing recently. 1) A long term bug in trigger handling gave a double free of the device. 2) Wrong return value handling means offsets are ignored in iio_convert_raw_to_processed_unlocked. 3) The iio_channel_has_info utility function was incorrectly updated during the recent info_mask split, this is now fixed. 4) mxs-lradc has a couple of little fixes. 5) A couple of missing .driver_module entries meant that drivers could be removed from underneath their users. 6) Error path fixes for ad7303 and lis3l02dq. 7) The scale value for presure in the lps331ap driver was out by a factor of 100.