linux-librem5 (5.7.19+librem5.1) amber-phone; urgency=medium

  [ Sebastian Krzyszkowiak ]
  * [e1d46f5] ASoC: wm8962: Export DAC/ADC monomix switches.
    This allows solutions like ALSA UCM to utilize hardware mono downmix
    for cases where mono output to a single speaker is desired only in
    specific situations (like on a mobile phone).
  * [72407c8] librem5_defconfig: Enable ashmem and binder for anbox support
  * [933c5c6] Merge tag 'v5.7.19' into stable/5.7.19.
    This is the 5.7.19 stable release

  [ Angus Ainslie (Purism) ]
  * [72fee32] arm64: configs: librem5_defconfig: configure the RFCOMM TTY
    device.  We need rfcomm tty for the gts1800 test fixture

  [ Guido Günther ]
  * Backport display subsystem from our 5.9 tree:
    * [1dad5b9] drm/bridge: nwl-dsi: Add support for video_pll.
    * [0630123] dt-bindings: display/bridge: nwl-dsi: Document video_pll clock.
    * [07b0406] drm/bridge: nwl-dsi: Add support for clock-drop-level.
    * [6d6768f] drm/bridge: nwl-dsi: add support for DCSS.
    * [9e90f8b] arm64: dts: imx8mq: Add video_pll to DSI host controller.
    * [eb84570] arm64: dts: librem5-devkit: Set clock drop level.
    * [982ff56] arm64: dts: librem5: Set clock drop level.
    * [68f3fbe] Revert "hack: mxsfb: half the pixel clock"

 -- Guido Günther <agx@sigxcpu.org>  Mon, 14 Sep 2020 09:51:20 +0200

linux-librem5 (5.7.14+librem5.2) amber-phone; urgency=medium

  [ Guido Günther ]
  * drm/mxsfb: Make supported modifiers explicit.
    In contrast to other display controllers on imx like DCSS and ipuv3
    lcdif/mxsfb does not support detiling e.g. vivante tiled layouts.
    Since mesa might assume otherwise make it explicit that only
    DRM_FORMAT_MOD_LINEAR is supported.
    (cherry picked from commit f4b29bf77319df18348b56e9fd87bc7d4266220e)
    This allows us to drop a downstream wlroots patch.
  * arm64: dts: imx8mq-librem5-r2: Sort alphabetically
  * arm64: dts: imx8mq-librem5-r3: Sort alphabetically
  * dt-bindings: iio: vcnl4000: convert bindings to YAML format.
    Convert the vcnl4000 device tree bindings to the new YAML format.
    (cherry picked from commit c194e2389d99be2fc69811693775b81f9ab88f6c)
  * dt-bindings: iio: Introduce common properties for iio sensors.
    Introduce a file for common properties of iio sensors. So far this
    contains the new proximity-near-level property for proximity sensors
    that indicates when an object should be considered near.
    (cherry picked from commit 445b16fb6bdc2cd3086a8d9018b4f325c89faa24)
  * dt-bindings: iio: light: vcnl4000: Add proximity-near-level.
    This value indicates when userspace should consider an object
    near to the sensor/device.
    (cherry picked from commit 138986062b50e7e24404e279d2e2c79c0291dac3)
  * Documentation: ABI: document IIO in_proximity_nearlevel file.
    The vcnl4000 IIO driver introduced a new attribute
    "in_proximity_nearlevel".  This adds it to the list of documented ABI
    for sysfs-bus-iio.
    (cherry picked from commit aa8cb0485594d8b3c9bfe7f4427b3ae26187c861)
  * iio: vcnl4000: Export near level property for proximity sensor.
    When an object can be considered close to the sensor is hardware
    dependent. Allowing to configure the property via device tree
    allows to configure this device specific value.
    This is useful for e.g. iio-sensor-proxy to indicate to userspace
    if an object is close to the sensor.
    (cherry picked from commit f5a98e1fca15cbf79f50098ea30e84ce33da2fd6)
  * arm64: dts: imx8mq-librem5.dtsi: Add alias for proximity sensor
  * arm64: dts: imx8mq-librem5-r3: Set proximity near level.
    This allows userspace to decide when an object is close.
  * arm64: dts: imx8mq-librem5-r2: Set proximity near level.
    This allows userspace to decide when an object is close.

  [ Martin Kepplinger ]
  * arm64: dts: imx8mq-librem5-r3: fix camera_pwr gpio
  * arm64: dts: imx8mq-librem5: camera1: add more useful comment.
    It's obviously a placeholder and disabled, no need to write that down.
  * arm64: dts: imx8mq-librem5: camera2: fix i2c address and add VCM.
    The rear facing camera is at 0x10 on the bus, not 0x2d. Also, descibe
    the voice coil motor we have.

 -- Guido Günther <agx@sigxcpu.org>  Tue, 18 Aug 2020 12:14:44 +0200