Tags

This is the 4.1.17 stable release

This is the 2.6.32.70 stable release

sound fixes for 4.5-rc2

There are a few fixes in ALSA core for bugs that have been spotted by
fuzzer.  Also a temporary workaround for PowerPC (and possibly other)
builds with incompatible ioctls was applied to compress API.

Other than that, a few trivial fixes and quirks for FireWire BeBoB,
USB-audio and HD-audio are found, too.

This is the 3.14.60 stable release

This is the 3.10.96 stable release

This is the 3.12.53 stable release

Here's a first set of fixes for the 4.5-rc cycle:
 * make regulatory messages much less verbose by default
 * various remain-on-channel fixes
 * scheduled scanning fixes with hardware restart
 * a PS-Poll handling fix; was broken just recently
 * bugfix to avoid buffering non-bufferable MMPDUs
 * world regulatory domain data fix
 * a fix for scanning causing other work to get stuck
 * hwsim: revert an older problematic patch that caused some
   userspace tools to have issues - not that big a deal as
   it's a debug only driver though

Linux 3.18.26

- support for v3 vbt dsi blocks (Jani)
- improve mmio debug checks (Mika Kuoppala)
- reorg the ddi port translation table entries and related code (Ville)
- reorg gen8 interrupt handling for future platforms (Tvrtko)
- refactor tile width/height computations for framebuffers (Ville)
- kerneldoc integration for intel_pm.c (Jani)
- move default context from engines to device-global dev_priv (Dave Gordon)
- make seqno/irq ordering coherent with execlist (Chris)
- decouple internal engine number from UABI (Chris&Tvrtko)
- tons of small fixes all over, as usual

Linux 4.5-rc1

This is the 4.3.4 stable release

This is the 4.1.16 stable release

This is the 3.14.59 stable release

This is the 3.10.95 stable release

This is the 3.2.76 stable release

sound fixes for 4.5-rc1

Here are lots of small fixes that have been collected since the
previous pull.  This time, not only trivial ones but fixes for some
serious bugs are included:
- Fix for CPU lockups by snd-hrtimer accesses
- Fix for unsafe disconnection handling in ALSA timer code
- Fix for Oops due to race at HD-audio module removal
- Fixes for possible memory corruption via 32bit PCM and sequencer
  compat ioctls
- Fix for regression in HD-audio generic model handling
- Suppress kernel warnings for invalid TLV ioctls that may flood up
- Fix the missing SSC clock handling for at73c213
- A pin fixup for ASUS N550JX

sound updates for 4.5-rc1

We've had quite busy weeks in this cycle.  Looking at ALSA core, the
significant changes are a few fixes wrt timer and sequencer ioctls
that have been revealed by fuzzer recently.  Other than that, ASoC
core got a few updates about DAI link handling, but these are rather
straightforward refactoring.

In drivers scene, ASoC received quite lots of new drivers in addition
to bunch of updates for still ongoing Intel Skylake support and
topology API.  HD-audio gained a new HDMI/DP hotplug notification via
component.  FireWire got a pile of code refactoring/updates with
SCS.1x driver integration.

More highlights are shown below.

[NOTE: this contains also many commits for DRM.  This is due to the
 pull of drm stable branch into sound tree, as the base of i915 audio
 component work for HD-audio.  The highlights below don't contain
 these DRM changes, as these are supposed to be pulled via drm tree in
 anyway sooner or later.]

Core
 - Handful fixes to harden ALSA timer and sequencer ioctls against
   races reported by syzkaller fuzzer
 - Irq description string can be unique to each card; only for
   HD-audio for now

ASoC
 - Conversion of the array of DAI links to a list for supporting
   dynamically adding and removing DAI links
 - Topology API enhancements to make everything more component based
   and being able to specify PCM links via topology
 - Some more fixes for the topology code, though it is still not final
   and ready for enabling in production; we really need to get to the
   point where that can be done
 - A pile of changes for Intel SkyLake drivers which hopefully deliver
   some useful initial functionality for systems with this chipset,
   though there is more work still to come
 - Lots of new features and cleanups for the Renesas drivers
 - ANC support for WM5110
 - New drivers: Imagination Technologies IPs, Atmel class D speaker,
   Cirrus CS47L24 and WM1831, Dialog DA7128, Realtek RT5659 and
   RT56156, Rockchip RK3036, TI PC3168A, and AMD ACP
 - Rename PCM1792a driver to be generic pcm179x

HD-Audio
 - Use audio component for i915 HDMI/DP hotplug handling
 - On-demand binding with i915 driver
 - bdl_pos_adj parameter adjustment for Baytrail controllers
 - Enable power_save_node for CX20722; this shouldn't lead to
   regression, hopefully
 - Kabylake HDMI/DP codec support
 - Quirks for Lenovo E50-80, Dell Latitude E-series, and other Dell
   machines
 - A few code refactoring

FireWire
 - Lots of code cleanup and refactoring
 - Integrate the support of SCS.1x devices into snd-oxfw driver;
   snd-scs1x driver is obsoleted

USB-audio
 - Fix possible NULL dereference at disconnection
 - A regression fix for Native Instruments devices

Misc
 - A few code cleanups of fm801 driver

GPIO bulk updates for the v4.5 kernel cycle:

Infrastructural changes:

- In struct gpio_chip, rename the .dev node to .parent to better reflect
  the fact that this is not the GPIO struct device abstraction. We will
  add that soon so this would be totallt confusing.

- It was noted that the driver .get_value() callbacks was
  sometimes reporting negative -ERR values to the gpiolib core, expecting
  them to be propagated to consumer gpiod_get_value() and gpio_get_value()
  calls. This was not happening, so as there was a mess of drivers
  returning negative errors and some returning "anything else than zero"
  to indicate that a line was active. As some would have bit 31 set to
  indicate "line active" it clashed with negative error codes. This is
  fixed by the largeish series clamping values in all drivers with
  !!value to [0,1] and then augmenting the code to propagate error codes
  to consumers. (Includes some ACKed patches in other subsystems.)

- Add a void *data pointer to struct gpio_chip. The container_of() design
  pattern is indeed very nice, but we want to reform the struct gpio_chip
  to be a non-volative, stateless business, and keep states internal to
  the gpiolib to be able to hold on to the state when adding a proper
  userspace ABI (character device) further down the road. To achieve this,
  drivers need a handle at the internal state that is not dependent on
  their struct gpio_chip() so we add gpiochip_add_data() and
  gpiochip_get_data() following the pattern of many other subsystems.
  All the "use gpiochip data pointer" patches transforms drivers to this
  scheme.

- The Generic GPIO chip header has been merged into the general
  <linux/gpio/driver.h> header, and the custom header for that removed.
  Instead of having a separate mm_gpio_chip struct for these generic
  drivers, merge that into struct gpio_chip, simplifying the code and
  removing the need for separate and confusing includes.

Misc improvements:

- Stabilize the way GPIOs are looked up from the ACPI legacy
  specification.

- Incremental driver features for PXA, PCA953X, Lantiq (patches from the
  OpenWRT community), RCAR, Zynq, PL061, 104-idi-48

New drivers:

- Add a GPIO chip to the ALSA SoC AC97 driver.

- Add a new Broadcom NSP SoC driver (this lands in the pinctrl dir, but
  the branch is merged here too to account for infrastructural changes).

- The sx150x driver now supports the sx1502.

The clk framework and driver changes for 4.5 look pretty typical. The
bulk of the changes are to clk controller drivers, though some
improvements to the core and some re-usable blocks/templates also
received some love. In this past cycle the clk maintainers developed a
good workflow for handling the common case of patch submissions
containing a new drivers, new shared Device Tree header and a new Device
Tree binding description. This requires coordination with the Device
Tree maintainers and with the architecture maintainers (typically the
arm-soc tree in our case). This explains the increase in changes to
include/dt-bindings/... and to
Documentation/devicetree/bindings/clock/... coming from the clk tree.
The same commits can be expected to come through those trees on
occasion, through the use of shared, immutable branches.