-
sunxi-drm-for-4.90c3ff44c · ·
Allwinner DRM changes for 4.9 This tag adds the support of a new SoC to sun4i-drm (the Allwinner A33), and the usual few fixes and enhancements
-
sunxi-dt-for-4.9-27a988a4d · ·
Allwinner DT changes for 4.9, take 2 A second set of device tree changes, this time switching a few SoCs to the new sunxi-ng clock framework. We also added the support for a new SoC (NextThing GR8 and its evaluation board), and the support for the DRM driver in the A33.
-
sunxi-clk-for-4.9d63a5e7c · ·
Allwinner Clock changes for 4.9 Four more SoCs converted to the new clock framework (A31, A31s, A23 and A33).
-
pm-4.8-rc68a2a835b · ·
Power management fixes for v4.8-rc6 - If the PM QoS framework invokes cancel_delayed_work_sync() during early boot, it will enable interrupts which is not expected at that point, so prevent it from happening (Tejun Heo). - Fix cpufreq statistic documentation to follow a recent change in behavior that forgot to update it as appropriate (Jean Delvare).
-
gpio-v4.8-356beac95 · ·
GPIO fixes for v4.8: - Revert a pointless attempt to add an include to solve the UM allyes compilation problem. - Make the mcp23s08 depend on OF_GPIO as it uses it and doesn't compile properly without it. - Fix a probing problem for ucb1x00.
-
sound-4.8-rc6816f318b · ·
sound fixes for 4.8-rc6 We've got quite a few fixes at this time, and all are stable patches. syzkaller strikes back again (episode 19 or so), and we had to plug some holes in ALSA core part (mostly timer). In addition, a couple of FireWire audio fixes for the invalid copy user calls in locks, and a few quirks for HD-audio and USB-audio as usual are included.
-
-
wireless-drivers-for-davem-2016-09-08a0714125 · ·
wireless-drivers fixes for 4.8 iwlwifi * fix P2P dump trigger * prevent a potential null dereference in iwlmvm * prevent an uninitialized value from being returned in iwlmvm * advertise support for channel width change in AP mode ath10k * fix racy rx status retrieval from htt context * QCA9887 support is not experimental anymore, remove the warning message ath9k * fix regression with led GPIOs * fix AR5416 GPIO access warning brcmfmac * avoid potential stack overflow in brcmf_cfg80211_start_ap()
-
-
sunxi-dt-for-4.9accfb2f1 · ·
Allwinner DT changes for 4.9 Business as usual on our side, with a mix of new boards and new IPs enabled on boards: - Support for the GPIO found on the AXP PMIC - ESP8089 on the relevant boards - More boards converted to the reference design and q8 designs - New boards: Orange Pi PC Plus, Orange Pi 2, Orange Pi Plus 2E, Orange Pi Lite, Olimex A33-Olinuxino, Empire Electronix M712, inet-d978_rev2, Nano Pi Neo
-
sunxi-fixes-for-4.8539d5c48 · ·
Allwinner fixes for 4.8 A single patch fixing a typo in the temperature trip points in the A13 DTSI.
-
sunxi-clk-fixes-for-4.86654674c · ·
Clock Fixes for the Allwinner SoCs, 4.8 Edition The usual bunch of fixes to the our clock drivers, mostly targetted to the brand new sunxi-ng drivers.
-
iio-fixes-for-4.8b171c0091 · ·
Second set of IIO fixes for the 4.8 cycle. We have a big rework of the kxsd9 driver queued up behind the fix below and a fix for a recent fix that was marked for stable. Hence this fix series is perhaps a little more urgent than average for IIO. * core - a fix for a fix in the last set. The recent fix for blocking ops when ! task running left a path (unlikely one) in which the function return value was not set - so initialise it to 0. - The IIO_TYPE_FRACTIONAL code previously didn't cope with negative fractions. Turned out a fix for this was in Analog's tree but hadn't made it upstream. * bmc150 - reset chip at init time. At least one board out there ends up coming up in an unstable state due to noise during power up. The reset does no harm on other boards. * kxsd9 - Fix a bug in the reported scaling due to failing to set the integer part to 0. * hid-sensors-pressure - Output was in the wrong units to comply with the IIO ABI. * tools - iio_generic_buffer: Fix the trigger-less mode by ensuring we don't fault out for having no trigger when we explicitly said we didn't want to have one.
-
-
regulator-fix-v4.8-rc578cefcbe · ·
regulator: Fixes for v4.8 Two things here, one an e-mail update for Krzysztof Kozlowski and the other a couple of fixes for issues with incorrectly described voltages in a couple of the Qualcomm regulator drivers that were breaking MMC on some platforms.