Tags

regulator: Fixes for v3.13

A small set of driver fixes plus one larger core change which changes
the way we check to see if we're using DT so that there aren't any races
between deciding we're using DT and the regulator subsystem noticing.
This makes the new support for substituting a dummy regulator and
optional regulators work a lot better on DT systems since it ensures
that we don't trigger probe deferral when we shouldn't which was causing
bugs in clients.

This is the 3.12.5 stable release

This is the 3.10.24 stable release

This is the 3.4.74 stable release

sound fixes for 3.13-rc4

Still a slightly high amount of changes than wished, but they are all
good regression and/or device-specific fixes.  Majority of commits are
for HD-audio, an HDMI ctl index fix that hits old graphics boards,
regression fixes for AD codecs and a few quirks.  Other than that, two
major fixes are included: a 64bit ABI fix for compress offload, and
64bit dma_addr_t truncation fix, which had hit on PAE kernels.

arm/smmu driver updates via Will Deacon fixing locking around page
table walks and a couple other issues.

This is the 3.12.4 stable release

This is the 3.10.23 stable release

This is the 3.4.73 stable release

Post-3.13-rc3 power management fixup

This reverts two cpufreq commits that fixed issues for some people,
but broke things for others, so revert them and we'll need to fix the
original problems differently.

/

Linux 3.13-rc3

Power management fixes for 3.13-rc3

 - cpufreq regression fix from Bjørn Mork restoring the pre-3.12
   behavior of the framework during system suspend/hibernation to
   avoid garbage sysfs files from being left behind in case of a
   suspend error.

 - PNP regression fix to restore the correct states of devices after
   resume from hibernation broken in 3.12.  From Dmitry Torokhov.

 - cpuidle fix to prevent cpuidle device unregistration from crashing
   due to a NULL pointer dereference if cpuidle has been disabled
   from the kernel command line.  From Konrad Rzeszutek Wilk.

 - intel_idle fix for the C6 state definition on Intel Avoton/Rangeley
   processors from Arne Bockholdt.

 - Power capping framework fix to make the energy_uj sysfs attribute
   work in accordance with the documentation.  From Srinivas Pandruvada.

 - epoll fix to make it ignore the EPOLLWAKEUP flag if the kernel has
   been compiled with CONFIG_PM_SLEEP unset (in which case that flag
   should not have any effect).  From Amit Pundir.

 - cpufreq fix to prevent governor sysfs files from being lost over
   system suspend/resume in some (arguably unusual) situations.  From
   Viresh Kumar.

/

Minor fbdev fixes for 3.13.

Pin control fixes for the v3.13 series:

- Minor bug fixes for the Rockchip, ST-Ericsson abx500,
  Renesas PFC r8a7740 and sh7372.

- Compilation warning fixes.

sound fixes for 3.13-rc3

A usual pattern of half ASoC and half HD-audio fixes, although
HD-audio fixups have more volumes, in addition to a couple of
trivial fixes.  Nothing to worry much is found here.

For ASoC side: a few fixes for PCM rate constraints calculations,
regmap byte-order fix, the rest driver specific fixes (atmel, fsl,
omap, kirkwood, wm codecs).

For HD-audio: Dell headset and mono out fix, ELD update in polling
mode, ALC283 Chromebook fixes, a few fixes for old AD codecs and
MBA2,1 regression fix.

This is the 3.12.3 stable release

This is the 3.10.22 stable release

This is the 3.4.72 stable release

GPIO fixes for the v3.13 series:

- Fix compile warnings.

- Fix overly talkative diagnostic messages from usual use
  cases wrt GPIO descriptors.

- Add a documentation 00-INDEX

- Use platform GPIOs as fallback when ACPI or device tree is
  used as the primary means to get GPIO lines.

- A bug fix for the MPC8572/MPC8536 fixing erroneous input data.

Second round of IIO fixes for the 3.13 cycle.

2 fixes here.

* The gp2ap020a00f is a simple missing kconfig dependency.

* The hid sensors hub fix is a work around for an issue introduced by hardware
changes due to a certain large software vendor having an 'interesting'
interpretation of the specification and hence indexing some arrays from 1
rather than 0.  The fix takes advantage of the logical min and max reading
facilities introduced by the precursor patch to figure out whether we have
a 0 indexed or 1 indexed device and to adjust appropriately.  It also
drops a previous kconfig option that allowed this issue to be worked around
at build time.