Tags

This is the 3.11.2 stable release

This is the 3.10.13 stable release

This is the 3.4.63 stable release

This is the 3.0.97 stable release

DeviceTree fixes for 3.12

Clean-up to fix some warnings for !OF builds and spelling fixes in docs

- Clean-up openrisc prom.h
- Fix warnings caused by of_irq.h ifdefs
- Spelling fix for Synopsys

Linux 3.12-rc2

First round of new drivers, functionality and cleanups for IIO in the 3.13 cycle

A number of new drivers and some new functionality + a lot of cleanups
all over IIO.

New Core Elements

1) New INT_TIME info_mask element for integration time, which may have
   different effects on measurement noise and similar, than an amplifier
   and hence is different from existing SCALE.  Already existed in some
   drivers as a custom attribute.

2) Introduce a iio_push_buffers_with_timestamp helper to cover the common
   case of filling the last 64 bits of data to be passed to the buffer with
   a timestamp.  Applied to lots of drivers. Cuts down on repeated code and
   moves a slightly fiddly bit of logic into a single location.

3) Introduce info_mask_[shared_by_dir/shared_by_all] elements to allow support
   of elements such as sampling_frequency which is typically shared by all
   input channels on a device.  This reduces code and makes these controls
   available from in kernel consumers of IIO devices.

New drivers

1) MCP3422/3/4 ADC

2) TSL4531 ambient light sensor

3) TCS3472/5 color light sensor

4) GP2AP020A00F ambient light / proximity sensor

5) LPS001WP support added to ST pressure sensor driver.

New driver functionality

1) ti_am335x_adc Add buffered sampling support.
   This device has a hardware fifo that is fed directly into an IIO kfifo
   buffer based on a watershed interrupt.  Note this will act as an example
   of how to handle this increasingly common type of device.
   The only previous example - sca3000 - take a less than optimal approach
   which is largely why it is still in staging.
   A couple of little cleanups for that new functionality followed later.

Core cleanups:

1) MAINTAINERS - Sachin actually brought my email address up to date because
   I said I'd do it and never got around to it :)

2) Assign buffer list elements as single element lists to simplify the
   iio_buffer_is_active logic.

3) wake_up_interruptible_poll instead of wake_up_interruptible to only wake
   up threads waiting for poll notifications.

4) Add O_CLOEXEC flag to anon_inode_get_fd call for IIO event interface.

5) Change iio_push_to_buffers to take a void * pointer so as to avoid some
   annoying and unnecessary type casts.

6) iio_compute_scan_bytes incorrectly took a long rather than unsigned long.

7) Various minor tidy ups.

Driver cleanups (in no particular order)

1) Another set of devm_ allocations patches from Sachin Kamat.

2) tsl2x7x - 0 to NULL cleanup.

3) hmc5843 - fix missing > in MODULE_AUTHOR

4) Set of strict_strto* to kstrto* conversions.

5) mxs-lradc - fix ordering of resource removal to match creation

6) mxs-lradc - add MODULE_ALIAS

7) adc7606 - drop a work pending test duplicated in core functions.

8) hmc5843 - devm_ allocation patch

9) Series of redundant breaks removed.

10) ad2s1200 - pr_err -> dev_err

11) adjd_s311 - use INT_TIME

12)  ST sensors - large set of cleanups from Lee Jones and removed restriction
    to using only triggers provided by the st_sensors themselves from
    Dennis Ciocca.

13) dummy and tmp006 provide sampling_frequency via info_mask_shared_by_all.

14) tcs3472 - fix incorrect buffer size and wrong device pointer used in
    suspend / resume functions.

15) max1363 - use defaults for buffer setup ops as provided by the triggered
    buffer helpers as they are the same as were specified in max1363 driver.

16) Trivial tidy ups in a number of other drivers.

First round of IIO fixes for 3.12

A series of wrong 'struct dev' assumptions in suspend/resume callbacks
following on from this issue being identified in a new driver review.
One to watch out for in future.

A number of driver specific fixes
1) at91 - fix a overflow in clock rate computation
2) dummy - Kconfig dependency issue
3) isl29018 - uninitialized value
4) hmc5843 - measurement conversion bug introduced by recent cleanup.
5) ade7854-spi - wrong return value.

Some IIO core fixes
1) Wrong value picked up for event code creation for a modified channel
2) A null dereference on failure to initialize a buffer after no buffer has
   been in use, when using the available_scan_masks approach.
3) Sampling not stopped when a device is removed. Effects forced removal
   such as hot unplugging.
4) Prevent device going away if a chrdev is still open in userspace.
5) Prevent race on chardev opening and device being freed.
6) Add a missing iio_buffer_init in the call back buffer.

These last few are the first part of a set from Lars-Peter Clausen who
has been taking a closer look at our removal paths and buffer handling
than anyone has for quite some time.

ACPI and power management fixes for 3.12-rc2

 1) Four fixes for cpufreq regressions introduced by the changes that
    removed Device Tree parsing for CPU device nodes from cpufreq
    drivers from Sudeep KarkadaNagesha.

 2) Two fixes for recent cpufreq regressions introduced by changes
    related to the preservation of sysfs attributes over system
    suspend/resume cycles from Viresh Kumar.

 3) Fix for ACPI-based wakeup signaling in the PCI subsystem that
    fails to stop PME polling for devices put into the D3cold power
    state from Rafael J Wysocki.

 4) Fix for bad interactions between cpufreq and udev on systems
    supporting intel_pstate where acpi-cpufreq is available as well
    from Yinghai Lu.

/

Linux 3.12-rc1

This is the 3.11.1 stable release

This is the 3.10.12 stable release

This is the 3.4.62 stable release

This is the 3.0.96 stable release

The highlights of the release are nested EPT and pv-ticketlocks
support (hypervisor part; guest part, which is most of the code, goes
through tip tree).  Apart of that there are many fixes for all arches.

IOMMU Updates for Linux v3.12

This round the updates contain:

	* A new driver for the Freescale PAMU IOMMU from Varun Sethi.
	  This driver has cooked for a while and required changes to the
	  IOMMU-API and infrastructure that were already merged before.
	* Updates for the ARM-SMMU driver from Will Deacon
	* Various fixes, the most important one is probably a fix from
	  Alex Williamson for a memory leak in the VT-d page-table
	  freeing code

In summary not all that much. The biggest part in the diffstat is the
new PAMU driver.

ACPI and power management fixes for 3.12-rc1

 1) ACPI-based PCI hotplug (ACPIPHP) fixes related to spurious events

  After the recent ACPIPHP changes we've seen some interesting breakage
  on a system that triggers device check notifications during boot for
  non-existing devices.  Although those notifications are really
  spurious, we should be able to deal with them nevertheless and that
  shouldn't introduce too much overhead.  Four commits to make that
  work properly.

 2) Memory hotplug and hibernation mutual exclusion rework

  This was maent to be a cleanup, but it happens to fix a classical
  ABBA deadlock between system suspend/hibernation and ACPI memory
  hotplug which is possible if they are started roughly at the same
  time.  Three commits rework memory hotplug so that it doesn't
  acquire pm_mutex and make hibernation use device_hotplug_lock
  which prevents it from racing with memory hotplug.

 3) ACPI Intel LPSS (Low-Power Subsystem) driver crash fix

  The ACPI LPSS driver crashes during boot on Apple Macbook Air with
  Haswell that has slightly unusual BIOS configuration in which one
  of the LPSS device's _CRS method doesn't return all of the information
  expected by the driver.  Fix from Mika Westerberg, for stable.

 4) ACPICA fix related to Store->ArgX operation

  AML interpreter fix for obscure breakage that causes AML to be
  executed incorrectly on some machines (observed in practice).  From
  Bob Moore.

 5) ACPI core fix for PCI ACPI device objects lookup

  There still are cases in which there is more than one ACPI device
  object matching a given PCI device and we don't choose the one that
  the BIOS expects us to choose, so this makes the lookup take more
  criteria into account in those cases.

 6) Fix to prevent cpuidle from crashing in some rare cases

  If the result of cpuidle_get_driver() is NULL, which can happen on
  some systems, cpuidle_driver_ref() will crash trying to use that
  pointer and the Daniel Fu's fix prevents that from happening.

 7) cpufreq fixes related to CPU hotplug

  Stephen Boyd reported a number of concurrency problems with cpufreq
  related to CPU hotplug which are addressed by a series of fixes
  from Srivatsa S Bhat and Viresh Kumar.

 8) cpufreq fix for time conversion in time_in_state attribute

  Time conversion carried out by cpufreq when user space attempts to
  read /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state won't
  work correcty if cputime_t doesn't map directly to jiffies.  Fix
  from Andreas Schwab.

 9) Revert of a troublesome cpufreq commit

  Commit 7c30ed5 (cpufreq: make sure frequency transitions are
  serialized) was intended to address some known concurrency problems
  in cpufreq related to the ordering of transitions, but unfortunately
  it introduced several problems of its own, so I decided to revert it
  now and address the original problems later in a more robust way.

10) Intel Haswell CPU models for intel_pstate from Nell Hardcastle.

11) cpufreq fixes related to system suspend/resume

  The recent cpufreq changes that made it preserve CPU sysfs attributes
  over suspend/resume cycles introduced a possible NULL pointer
  dereference that caused it to crash during the second attempt to
  suspend.  Three commits from Srivatsa S Bhat fix that problem and a
  couple of related issues.

12) cpufreq locking fix

  cpufreq_policy_restore() should acquire the lock for reading, but
  it acquires it for writing.  Fix from Lan Tianyu.

/

This is the 3.2.51 stable release

VFIO updates include safer default file flags for VFIO device fds,
an external user interface exported to allow other modules to hold
references to VFIO groups, a fix to test for extended config space
on PCIe and PCI-x, and new hot reset interfaces for PCI devices
which allows the user to do PCI bus/slot resets when all of the
devices affected by the reset are owned by the user.

For this last feature, the PCI bus reset interface, I depend on
changes already merged from Bjorn's PCI pull request.  I therefore
merged my tree up to commit cb3e433, which I think was the correct
action, but as Stephen Rothwell noted, I failed to provide a commit
message indicating why the merge was required.  Sorry for that.
Thanks,
Alex

This is the 3.10.11 stable release