Tags give the ability to mark specific points in history as being important
-
iio-for-3.9a
e07c6d17 · ·First round of IIO new stuff and cleanups for 3.9 Here we have: * RTC driver for the hid-sensor hubs. This is routed through here with agreement of Jiri Kosina and Andrew Morton. * Some small patches doing dead code removal and fixing some comments. * max1363 - move to the triggered_buffer helpers (basically duplicate code removal). * lp8788 - parent device change from the i2c device to the intermediate mfd. So the bulk of what we have is actually outside the IIO tree but the RTC driver in question is dependent on some patches that directly effect IIO so I am routing it through IIO with the agreement of the relevant maintainers (Andrew is acting as maintainer of RTC at the moment). The majority of HID-sensor related code is in IIO and it now crosses 3 subsystems so it was going to be a bit awkward whatever route it took.
-
iio-fixes-for-3.8a
678fb42e · ·First round of fixes for IIO post 3.8-rc1. A set of worthy if rather dull little fixes. * A whole set of incorrect error handling on regulator voltage requests. * An error in the probe path for max1363. * A couple of Kconfig issues with missing/ignored dependencies. * A nasty shift vs compare typo in adf4350 * Bug fixes for a silly error that prevents at91_adc driver building.
-
iommu-updates-v3.8
9c6ecf6a · ·IOMMU Updates for Linux v3.8 A few new features this merge-window. The most important one is probably, that dma-debug now warns if a dma-handle is not checked with dma_mapping_error by the device driver. This requires minor changes to some architectures which make use of dma-debug. Most of these changes have the respective Acks by the Arch-Maintainers. Besides that there are updates to the AMD IOMMU driver for refactor the IOMMU-Groups support and to make sure it does not trigger a hardware erratum. The OMAP changes (for which I pulled in a branch from Tony Lindgren's tree) have a conflict in linux-next with the arm-soc tree. The conflict is in the file arch/arm/mach-omap2/clock44xx_data.c which is deleted in the arm-soc tree. It is safe to delete the file too so solve the conflict. Similar changes are done in the arm-soc tree in the common clock framework migration. A missing hunk from the patch in the IOMMU tree will be submitted as a seperate patch when the merge-window is closed.
-
-
regulator-3.8
4ffc45c3 · ·regulator: Updates for v3.8 A fairly quiet release again, a couple of relatively small new features and a bunch of driver specific work including yet more code elimination and fixes from Axel Lin. - Addidion of linear_min_sel for offsetting linear selectors in the helpers. - Support for continuous voltage ranges for regulators with extremely high resolution. - Drivers for AS3711, DA9055, MAX9873, TPS51632, TPS80031 and ARM vexpress.
-
pm+acpi-for-3.8-rc1
f316fc56 · ·ACPI and power management updates for 3.8-rc1 * Introduction of device PM QoS flags. * ACPI device power management update allowing subsystems other than PCI to use it more easily. * ACPI device enumeration rework allowing additional kinds of devices to be enumerated via ACPI. From Mika Westerberg, Adrian Hunter, Mathias Nyman, Andy Shevchenko, and Rafael J. Wysocki. * ACPICA update to version 20121018 from Bob Moore and Lv Zheng. * ACPI memory hotplug update from Wen Congyang and Yasuaki Ishimatsu. * Introduction of acpi_handle_<level>() messaging macros and ACPI-based CPU hot-remove support from Toshi Kani. * ACPI EC updates from Feng Tang. * cpufreq updates from Viresh Kumar, Fabio Baltieri and others. * cpuidle changes to quickly notice governor prediction failure from Youquan Song. * Support for using multiple cpuidle drivers at the same time and cpuidle cleanups from Daniel Lezcano. * devfreq updates from Nishanth Menon and others. * cpupower update from Thomas Renninger. * Fixes and small cleanups all over the place. --
-
iio-for-3.8f
583f2deb · ·6th set of IIO new driver support, clean up and fixes for the 3.8 cycle (possibly wait until 3.9 cycle given timing). Here we have * the cleanup and move out of staging of ad7793. * addition support for additional parts to ad7793. * a basic new driver for TI ADC081C021/027 * 4 little fixes for the recent addition of ad16136 and ad16480. So some nice work with nothing controversial or anything that will effect stuff outside the drivers in question.
-
ixp4xx-fixes
0d2c9f05 · ·ARM: ixp4xx bug fixes These were originally prepared by Krzysztof Halasa but not submitted in time for v3.7 due to some confusion about how ixp4xx patches should be handled. Jason Cooper thankfully offered to help out sending the patches upstream through arm-soc now, but given the timing, we could as well delay them for 3.8.
-
pm-for-3.7-rc7
a7227a0f · ·Power management update for 3.7-rc7 Fix for an incorrect error condition check in device PM QoS code that may lead to an Oops from Guennadi Liakhovetski.
-
iio-for-3.8e
be7fd3b8 · ·Fifth round of new IIO drivers, cleanups and fixes for the 3.8 cycle. Here we have a number of minor fixes. * a quirk for the hid sensor driver should be a boolean option. * return an error for a failed memdup in the hid sensor driver. * Fix a return value in adt7410. * A double free in the IIO event infrastructure. * Disabling interrupts in tsl2563 was wrong (never been correct!) * Incorrect signature for the iio_buffer_register stub * Incorrect return for isl29018 write_raw callback. * A number of minor fixes as part of the various rework series. New drivers and major rework. * Introduce and use extensively an adis library for numerous spi Analog Devices mems sensors. This then moves out of staging. * Lots of new stuff then added to this library to support newer sensors. * New drivers for ADIS16136 and ADIS16480 and similar. * Core support for barometric pressure sensors. * ad7298 cleanup and move out of staging. The bulk of this is from Lars-Peter Clausen. He's been rather busy!
-
iommu-fixes-v3.7-rc6
3da4af0a · ·IOMMU fixes for Linux 3.7-rc6 Some fixes and a MAINTAINERS update to remove my lost AMD email address from the file. The fixes take care of a resource leak and a problem on VT-d with the new IOMMU group code.