-
miphy365x_dt_common_headerd821bfa4 · ·
miphy365x_dt_header This provides the shared header file which will be referenced from both the MiPHY365x driver and its associated Device Tree node(s).
-
asoc-v3.16-rc5d0ab92d6 · ·
ASoC: Fixes for v3.16 A bigger batch of changes than I would like as I didn't send any for a few weeks without noticing how many had built up. They are almost all driver specific though, larger changes are: - Fixes to the newly added Baytrail/MAX98090 which look like some QA was missed on the microphone detection. - Deletion of some erroniously listed audio formats for Haswell. - Fix debugfs creation in the core so that we don't try to generate multiple directories with the same name, relatively large textually but simple to inspect by eye and test. - A couple of bugfixes for the rcar driver one of which which involves a bit of code motion to move initailisation of some hardware out of common paths into device specific ones. - Ensure both channels are powered up for mono outputs on Arizona devices, involving some simple data tables listing the outputs and a loop over them. - A couple of fixes to save and restore information on suspended and idle Samsung I2S controllers.
-
iio-fixes-for-3.16e9b2a4d35 · ·
Fifth set of fixes for IIO in the 3.16 cycle. One nasty one that has been around a long time and a couple of non compliant ABI fixes. * The demux code used to split out desired channels for devices that only support reading sets of channels at one time had a bug where it was building it's conversion tables against the wrong bitmap resulting in it never actually demuxing anything. This is an old bug, but will be effecting an increasing number of drivers as it is often used to avoid some fiddly code in the individual drivers. * bma180 and mma8452 weren't obeying the ABI wrt to units for acceleration. Were in G rather than m/s^2. A little input check was missing from bma180 that might lead to acceptance of incorrect values. This last one is minor but might lead to incorrect userspace code working and problems in the future.
-
sunxi-clocks-for-3.176c1d66f0 · ·
Allwinner clocks additions for 3.17 This pull request adds support for the clocks found in the newly supported Allwinner A23 clocks.
-
sunxi-core-for-3.175ba1657e · ·
Allwinner core additions for 3.17 Nothing very fancy here, only the introduction from the new Allwinner A23 SoC.
-
sunxi-dt-for-3.17c220aec2 · ·
Allwinner DT additions for 3.17 Among the few patches that we have so far, there's a few noticeable changes: - Introduction of the Allwinner A23 SoC - Support for the GMAC on the A31. This is only available so far on the boards which bootloader enable the PHY regulator. - Addition of the infrared receiver
-
-
iommu-fixes-v3.16-rc53170447c · ·
IOMMU Fixes for Linux v3.16-rc5 A couple of fixes for the Freescale PAMU driver queued up: * Fix PAMU window size check. * Fix the device domain attach condition. * Fix the error condition during iommu group
-
pm+acpi-3.16-rc639628080 · ·
ACPI and power management fixes for 3.16-rc6 - Fix for a recently introduced NULL pointer dereference in the core system suspend code occuring when platforms without ACPI attempt to use the "freeze" sleep state from Zhang Rui. - Fix for a recently introduced build warning in cpufreq headers from Brian W Hart. - Fix for a 3.13 cpufreq regression related to sysem resume that triggers on some systems with multiple CPU clusters from Viresh Kumar. - Fix for a 3.4 regression in request_firmware() resulting in WARN_ON()s on some systems during system resume from Takashi Iwai. - Revert of the ACPI video commit that changed the default value of the video.brightness_switch_enabled command line argument to 0 as it has been reported to break existing setups. - ACPI device enumeration documentation update to take recent code changes into account and make the documentation match the code again from Darren Hart. - Fixes for the sa1110, imx6q, kirkwood, and cpu0 cpufreq drivers from Linus Walleij, Nicolas Del Piano, Quentin Armitage, Viresh Kumar. - New ACPI video blacklist entry for HP ProBook 4540s from Hans de Goede. /
-
at91-drivers-for-3.17ae499f0f · ·
AT91 reset, poweroff and ram drivers This tag holds the various new drivers introduced to move code that used to be in mach-at91 over to the proper frameworks. These files are the reboot and poweroff code for all AT91 SoCs but the RM9200, and the ram controller driver is not doing much at the time, except for grabing the RAM clock in order to leave it always enabled.
-
at91-dt-for-3.1716aa7f1f · ·
AT91 ramc and reset/poweroff related DT patches This branch gathers a few devicetree patches needed for the reworks found in the later patches to be sent. More precisely, it holds: - The addition of ddrck for the sama5d3 and the sam9 SoCs - The addition of the shutdown controller node in the sama5d3 DTSI - The slight rework of the ramc bindings for the SoCs that have several RAM controllers
-
sound-3.16-rc64da63c6f · ·
sound fixes for 3.16-rc6 Things seem to calm down so far, just a small few HD-audio fixes (regression fixes and a new codec ID addition) popping up.
-
gpio-v3.16-3ef8290ac · ·
A GPIO fix for the v3.16 series - fixes up some merge confusion from the merge window.
-