Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • mac80211-for-davem-2016-06-09
    Two more fixes for now:
     * a fix for a long-standing iwpriv 32/64 compat issue
     * two fairly recently introduced (4.6) warning asking for
       symmetric operations are erroneous and I remove them
    
  • iio-for-4.8a
    First round of IIO new device support, features and cleanups for the 4.8 cycle.
    
    New device support
    * ads1015
      - add ads1115 support
    * bma220 accelerometer
      - new driver
      - triggered buffer support.
    * bmc150
      - add bmm150 support.
    * bmp280
      - bme280 support with addition of humidity channel.
    * max5487 potentiometer
      - new driver
    * MMA7660FC accelerometer.
      - New driver
    * st-pressure
      - support for the lps22hb
    * loop trigger.
      - This one is *nasty* but we have real applications (parrot drones) where
      it is useful.  The trigger basically spins as hard as it can firing off
      a new trigger each time all triggered devices come back to say they are
      done.  It doesn't hang a machine even when doing it on a dummy driver.
      A lot nicer than having this implemented within lots of device drivers
      anyway.
    
    Core stuff
    * Add support to create IIO devices via configfs (similar to we did for
    triggers a while back) + docs.
    * New channel types
      - IIO_ELECTRICAL_CONDUCTIVITY
    * Couple of MAINTAINERS patches to list the device tree bindings.
    * Make trigger ops structure non optional (comment fix). It hasn't been for
    an awful long time, but that's not what the description said.
    
    New features
    * ak8975
      - support adapters that are limited to byte data only by allowing the
      emulated block read i2c function that was recently introduced.
    * atlas-ph
      - support atlas-ec (electrical conductivity sensor)
    * bmi160
      - add available frequency and scale attributes to make the driver
      more user friendly (and avoid having to read the datasheet to know
      what will work).
    * dummy
      - move creation to configfs interface.  It's not real hardware so we
      are not that worried about the ABI breakage ;)
    * mma8452
      - oversampling ration support
    * nau7802
      - expose available gains to make life easier for userspace.
    * st-sensors
      - allow use of emulation for SMBus block reads as all the st parts support
      it.
    * ti-ads1015
      - list datasheet names to allow their use by inkernel consumers.
    * Various module alias additions to help auto probing.  Drop one redundant one
    as well.
    
    Cleanups
    * ad7266, ad7476, ad7887, ad7923, ad799x
      - use direct mode claim function rather than open coding it during sensor
      read (prevents switching on buffers mid read).
    * ad7793, ad7791
      - use direct mode claim to prevent frequency changes when buffers running.
    * afe440x - These are ABI breaking but the driver requires custom userspace
      code to do anything useful anyway and that is still being written and under
      control of TI.  Ultimately we may have other libraries to do pulse
      oximetry with these devices but we aren't aware of any yet.
      - kernel-doc format fixes
      - drop ifdef fun around of_match_ptr - it's not worth the mess to save
      a tiny amount of space.
      - drop some unnecessary register initializations.
      - drop the weird locked gain modes as they gain us nothing (can just set
      all gains separately).
      - remove handling of offset attributes seeing as no channels actually have
      them (oops)
      - Drop the LED3 input channel as it's an alias for ALED2.
      - *big one* remove channel names - an experiment that turned out to not
      make sense - see patch for details.
      - use regmap fields to clean up code.
      - tie the tia gain stages to appropriate channels in the ABI as that is
      what they really effect. Same with the LED currents.
      - cleanout some unused defines and fix a missnamed one.
    * atlas-ph
      - reorganise to allow support of other similar parts.
    * bmc150
      - document supported chips in kconfig help.
    * jsa1212
      - drop an unneeded i2c functionality check for functionality the driver
      doesn't use.
    * mxs-lradc
      - simply touch screen registration code.
      - remove the touch screen unregister as all devm based now.
      - disable only those channels that are masked in hardware stop (others
      are already dealt with elsewhere)
    * st-sensors
      - unexport st_sensors_get_buffer_element as nothing outside the st-sensors
      core driver uses it.
      - fix handling of failure to start up regulators.
    * tpl0102
      - drop an i2c functionality test for features that aren't needed.
    * ti-am335x
      - use variable name rather than type in sizeof for clarity.
      - use SIMPLE_DEV_PM_OPS helper macro to tidy up a bit.
    
    Tools
    * Add install / uninstall to makefile.  Someone cares, so presumably
    some people will find it useful!
    *  generic_buffer
       - rename to iio_generic_buffer to line up with other tools.
       - handle cleanup when receiving signals
       - Add a --device-num option and a --trigger-num option rather than
       relying on naming which doesn't work if you have two of the same part.
    
  • v4.6.2
    536b1f59 · Linux 4.6.2 ·
    This is the 4.6.2 stable release
    
  • v4.5.7
    8c596d17 · Linux 4.5.7 ·
    This is the 4.5.7 stable release
    
  • v4.4.13
    ba760d43 · Linux 4.4.13 ·
    This is the 4.4.13 stable release
    
  • v3.14.72
    022aafd0 · Linux 3.14.72 ·
    This is the 3.14.72 stable release
    
  • topic/drm-misc-2016-06-07
  • iio-fixes-for-4.7a
    First round of iio fixes for the 4.7 cycle.
    
    A slightly bumper set due to travel delaying the pull request and a fair few
    issues with the recent merge window patches.  Patches all over the place.
    The st-sensors one is probably the most involved, but definitly solves the
    issues seen.  Note there are some other issues around that handler
    (and the fact that a lot of boards tie a level interrupt chip to an
    edge interrupt only irq chip).  These are not regressions however, so
    will turn up the slow route.
    
    * core
      - iio_trigger_attach_pollfunc had some really badly wrong error handling.
      Another nasty triggered whilst chasing down issues with the st sensors
      rework below.
    * ad5592r
      - fix an off by one error when allocating channels.
    * am2315
      - a stray mutex unlock before we ever take the lock.
    * apds9960
      - missing a parent in the driver model (which should be the i2c device).
      Result is it doesn't turn up under /sys/bus/i2c/devices which some
      userspace code uses for repeatable device identification.
    * as3935
      - ABI usage bug which meant a processed value was reported as raw. Now
        reporting scale as well to ensure userspace has the info it needs.
      - Don't return processed value via the buffer - it doesn't conform to
        the ABI and will overflow in some cases.
      - Fix a wrongly sized buffer which would overflow trashing part of the
        stack.  Also move it onto the heap as part of the fix.
    * bh1780
      - a missing return after write in debugfs lead to an incorrect read and
        a null pointer dereference.
      - dereferencing the wrong pointer in suspend and resume leading to
        unpredictable results.
      - assign a static name to avoid accidentally ending up with no name if
        loaded via device tree.
    * bmi160
      - output data rate for the accelerometer was incorrectly reported. Fix it.
      - writing the output data rate was also wrong due to reverse parameters.
    * bmp280
      - error message for wrong chip ID gave the wrong expected value.
    * hdc100x
      - mask for writing the integration time was wrong allowin g us to get
      'stuck' in a particular value with no way back.
      - temperature reported in celsius rather than millicelsius as per the
      ABI.
      - Get rid of some incorrect data shifting which lead to readings being
      rather incorrect.
    * max44000
      - drop scale attribute for proximity as it is an unscaled value (depends
        on what is in range rather than anything knowable at the detector).
    * st-pressure
      - ABI compliance fixes - units were wrong.
    * st-sensors
      - We introduced some nasty issues with the recent switch over to a
      a somewhat threaded handler in that we broke using a software trigger
      with these devices.  Now do it properly.  It's a larger patch than ideal
      for a fix, but the logic is straight forward.
      - Make sure the trigger is initialized before requesting the interrupt.
      This matters now the interrupt can be shared. Before it was ugly and wrong
      but short of flakey hardware could not be triggered.
      - Hammer down the dataready pin at boot - otherwise with really
      unlucky timing things could get interestingly wedged requiring a hard power
      down of the chip.
    
  • v3.18.35
    b5076139 · Linux 3.18.35 ·
    Linux 3.18.35
    
  • v4.1.26
    88817286 · Linux 4.1.26 ·
    Linux 4.1.26
    
  • drm-intel-next-2016-06-06
    - some polish for the guc code (Dave Gordon)
    - big refactoring of gen9 display clock handling code (Ville)
    - refactoring work in the context code (Chris Wilson)
    - give encoder/crtc/planes useful names for debug output (Ville)
    - improvements to skl/kbl wm computation code (Mahesh Kumar)
    - bunch of smaller improvements all over as usual
  • v4.7-rc2
    af8c34ce · Linux 4.7-rc2 ·
    Linux 4.7-rc2
    
  • wireless-drivers-for-davem-2016-06-04
    wireless-drivers fixes for 4.7
    
    brcmfmac
    
    * add fallback RSSI report for devices that do not report per-chain values
    * fix a null pointer derefence regression on PCIe full dongle devices
    
    rtlwifi
    
    * fix scheduling while atomic regression from commit 49f86ec21c01
    
    MAINTAINERS
    
    * add file patterns for wireless device tree bindings
    
  • acpi-4.7-rc2
    ACPI fixes for v4.7-rc2
    
     - Fix an incorrect check introduced by recent ACPICA changes which
       causes problems with booting KVM guests to happen, among other
       things (Lv Zheng).
    
     - Fix a backlight issue introduced by recent changes to the ACPI
       video driver (Aaron Lu).
    
     - Fix the ACPI processor initialization which attempts to register
       an IO region without checking if that really is necessary and
       sometimes prevents drivers loaded subsequently from registering
       their resources which leads to boot issues (Rafael Wysocki).
    
  • pm-4.7-rc2
    Power management fixes for v4.7-rc2
    
     - Fix a silly mistake related to the clamp_val() usage in
       a function added by a recent commit (Rafael Wysocki).
    
     - Reduce the log level of an annoying message added to intel_pstate
       during the recent merge window (Srinivas Pandruvada).
    
  • drm-fixes-for-v4.7-rc2
  • v4.6.1
    d3c1ffd7 · Linux 4.6.1 ·
    This is the 4.6.1 stable release
    
  • v4.5.6
    ec2a7555 · Linux 4.5.6 ·
    This is the 4.5.6 stable release
    
  • v4.4.12
    351d2d4d · Linux 4.4.12 ·
    This is the 4.4.12 stable release
    
  • v3.14.71
    f06cb456 · Linux 3.14.71 ·
    This is the 3.14.71 stable release