-
-
sound-4.9-rc1
sound updates for 4.9-rc1 Again the diffstat shows a widely distributed pattern at this cycle, as there've been many code cleanups and refactoring allover the places. Other than that, the development was relatively calm, and no big surprise shouldn't be expected. Here are some highlights: Core: - Sequencer code refactoring / documentation updates - TLV code moved to uapi, following some relevant cleanups USB-Audio: - Lots of LINE6 driver fixes / updates - DragonFly and TEAC device quirk updates HD-audio: - Usual fixupes for Dell, Lenovo and HP machines - Link-audio time reporting capability ASoC: - Large refactoring of simple-card code to be shared with rcar driver - Removal of some duplicated ops over lots of CODEC drivers - Again quite a few Intel SKL driver updates - New drivers for Nuvoton NAU88C10, Realtek RT5660 and RT5663
-
devicetree-for-4.987e5fc99 · ·
DeviceTree updates for 4.9: - Update changeset documentation on locking to reflect current code - Fix alphabetizing of vendor-prefixes.txt - Add various vendor prefixes - Add ESP8089 WiFi binding - Add new variable sized array parsing functions
-
gpio-v4.9-1e0852940 · ·
This is the bulk of GPIO changes for the v4.9 series: Subsystem improvements: - Do away with the last users of the obsolete Kconfig options ARCH_REQUIRE_GPIOLIB and ARCH_WANT_OPTIONAL_GPIOLIB (the latter always sounded like an item on a wishlist to Santa Claus to me). We can now select GPIOLIB and be done with it, for all archs. After some struggle it even work on UM. Not that it has GPIO, but if it wants to, it can select the library. - Continued efforts to make drivers properly either tristate or bool. - Introduce a warning for drivers assigning default triggers to their irqchip lines when probed from device tree, so we find and fix these ambigous drivers. It is agreed that in the OF config path, the device tree defines trigger characteristics. - The same warning, mutatis mutandis, for ACPI-probed GPIO irqchips. - We introduce the ability to mark certain IRQ lines as "unusable" as they can be taken by BIOS/firmware, unrouted in silicon and generally nasty if you use them, and such things. This is put to good use in the STMPE driver and also in the Cherryview pin control driver. - A new "mockup" virtual GPIO device that can be used for testing. The plan is to add unit tests under tools/* for exercising this device and verify that the kernel code paths are working as they should. - Make memory-mapped I/O-drivers depend on HAS_IOMEM. This was implicit all the time, but when people started building UM with allyesconfig or allmodconfig it exploded in their face. - Move some stray bits of device tree and ACPI HW description callbacks down into their respective implementation silo. These were causing issues when compiling on !HAS_IOMEM as well, so now eventually UM compiles the GPIOLIB library if it wants to. New drivers: - New driver for the Aspeed GPIO front-end companion to the pin controller merged through the pin control tree. - New driver for the LP873x PMIC GPIO portions. - New driver for Technologic Systems' I2C FPGA GPIO such as TS4900, TS-7970, TS-7990 and TS-4100. - New driver for the Broadcom BCM63xx series including BCM6338 and BCM6345. - New driver for the Intel WhiskeyCove PMIC GPIO. - New driver for the Allwinner AXP209 PMIC GPIO portions. - New driver for Diamond Systems 48 line GPIO-MM, another of these port-mapped I/O expansion cards. - Support the STMicroelectronics STMPE1600 variant in the STMPE driver. Driver improvements: - The STMPE driver now supports rising/falling edge detection properly for IRQs. - The PCA954x will now fetch and enable its VCC regulator properly. - Major rework of the PCA953x driver with the goal of eventually switching it over to use regmap and thus modernize it even more. - Switch the IOP driver to use the generic MMIO GPIO library. - Move the ages old HTC EGPIO (extended GPIO) GPIO expander driver over to this subsystem from MFD, achieveing some separation of concerns.
-
regulator-v4.92ed89d57 · ·
regulator: Changes for v4.9 This is an extremely quiet release for the regulator API, we've got a small set of bug fixes and minor feature enhancements for drivers plus a couple of more visible changes: - Add support for ramp times in regulators that don't use selectors. - New driver for LTC3676.
-
mac80211-next-for-davem-2016-10-041e1430d5 · ·
This time around, we have * Neighbor Awareness Networking (NAN) APIs * a fix for a previous patch that caused memory corruption in wireless extensions key settings * beacon rate configuration for AP and mesh * memory limits for mac80211's internal TXQs * a (fairly involved) fix for the TXQ vs. crypto problems * direct cfg80211 driver API for WEP keys This also pulls in net-next to fix the merge conflicts, see the merge commit for more details.
-
-
asoc-v4.9513e43ef · ·
ASoC: Updates for v4.9 Apart from the cleanups done by Morimoto-san this has very much been a driver focused release with very little generic change: - A big factoring out of the simple-card code to allow it to be shared more with the rcar generic card from Kuninori Morimoto. - Removal of some operations duplicated on the CODEC level, again by Kuninori Morimoto. - Lots more machine support for x86 systems. - New drivers for Nuvoton NAU88C10, Realtek RT5660 and RT5663.
-
mac80211-next-for-davem-2016-09-30bb42f2d1 · ·
This time around, we have * Neighbor Awareness Networking (NAN) APIs * a fix for a previous patch that caused memory corruption in wireless extensions key settings * beacon rate configuration for AP and mesh * memory limits for mac80211's internal TXQs * a (fairly involved) fix for the TXQ vs. crypto problems * direct cfg80211 driver API for WEP keys
-