1. 13 10月, 2017 4 次提交
    • D
      Merge tag 'omapdrm-4.15' of git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux into drm-next · 972805c1
      Dave Airlie 提交于
      omapdrm changes for 4.15
      
      * OMAP4 HDMI CEC support
      
      * tag 'omapdrm-4.15' of git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux:
        omapdrm: omapdss_hdmi_ops: add lost_hotplug op
        omapdrm: hdmi4: hook up the HDMI CEC support
        omapdrm: hdmi4_cec: add OMAP4 HDMI CEC support
        omapdrm: hdmi4: refcount hdmi_power_on/off_core
        omapdrm: hdmi4: move hdmi4_core_powerdown_disable to hdmi_power_on_core()
        omapdrm: hdmi4: prepare irq handling for HDMI CEC support
        omapdrm: hdmi4: make low-level functions available
        omapdrm: hdmi.h: extend hdmi_core_data with CEC fields
        omapdrm: encoder-tpd12s015: keep ls_oe_gpio high
      972805c1
    • D
      Merge tag 'drm-misc-next-2017-10-12' of git://anongit.freedesktop.org/drm/drm-misc into drm-next · d0f6d401
      Dave Airlie 提交于
      More 4.15 drm-misc stuff:
      
      Cross-subsystem Changes:
      - bridge cleanup refactor (Benjamin Gaignard)
      
      Core Changes:
      - less surprising atomic iterators (Maarten), fixes an oops introduced
        in drm-next
      - better gem/fb helper docs (Noralf)
      - fix dma-buf rcu races (Christian König)
      
      Driver Changes:
      - adv7511: CEC support (Hans Verkuil)
      - sun4i update from Chen-Yu to improve hdmi and A31 support
      - sii8620: add remote control support (Maceiej Purski)
      
      New drivers:
      - SiI9234 bridge driver (Maciej Purski)
      - 7" rpi touch panel (Eric Anholt)
      
      Note that this contains a topic pull from regmap, needed by the sun4i
      changes. Mark Brown sent that out for pulling into drm-misc.
      
      * tag 'drm-misc-next-2017-10-12' of git://anongit.freedesktop.org/drm/drm-misc: (29 commits)
        drm/dp: WARN about invalid/unknown link rates and bw codes
        drm/msm/mdp5: remove less than 0 comparison for unsigned value
        drm/bridge/sii8620: add remote control support
        drm/sun4i: hdmi: Add support for A31's HDMI controller
        drm/sun4i: hdmi: Add A31 specific DDC register definitions
        drm/sun4i: hdmi: Add support for controller hardware variants
        dt-bindings: display: sun4i: Add binding for A31 HDMI controller
        drm/sun4i: hdmi: Allow using second PLL as TMDS clk parent
        drm/sun4i: hdmi: create a regmap for later use
        drm/sun4i: hdmi: Disable clks in bind function error path and unbind function
        drm/sun4i: tcon: Add support for demuxing TCON output on A31
        drm/sun4i: tcon: Add variant callback for TCON output muxing
        drm/bridge/synopsys: dsi :remove is_panel_bridge
        drm/vc4: remove bridge from driver internal structure
        drm/stm: ltdc: remove bridge from driver internal structure
        drm/drm_of: add drm_of_panel_bridge_remove function
        drm/bridge: make drm_panel_bridge_remove more robust
        dma-fence: fix dma_fence_get_rcu_safe v2
        dma-buf: make reservation_object_copy_fences rcu save
        drm/atomic: Unref duplicated drm_atomic_state in drm_atomic_helper_resume()
        ...
      d0f6d401
    • A
      drm: vblank: remove drm_timestamp_monotonic parameter · 25e1a798
      Arnd Bergmann 提交于
      There is a risk of overflowing vblank timestamps in 2038 or 2106 if
      someone sets the drm_timestamp_monotonic module parameter to zero.
      
      I found no indication of anyone ever setting the parameter, or
      complaining about the default being wrong, after it was introduced
      as a way to handle backwards-compatibility with linux prior to
      c61eef72 ("drm: add support for monotonic vblank timestamps"),
      so it's probably safer to just remove the parameter completely
      and only allowing the default behavior.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NDaniel Stone <daniels@collabora.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      25e1a798
    • A
      drm: vblank: use ktime_t instead of timeval · 67680d3c
      Arnd Bergmann 提交于
      The drm vblank handling uses 'timeval' to store timestamps in either
      monotonic or wall-clock time base. In either case, it reads the current
      time as a ktime_t in get_drm_timestamp() and converts it from there.
      
      This is a bit suspicious, as users of 'timeval' often suffer from
      the time_t overflow in y2038. I have gone through this code and
      found that it is unlikely to cause problems here:
      
      - The user space ABI does not use time_t or timeval, but uses
        'u32' and 'long' as the types. This means at least that rebuilding
        user programs against a new libc with 64-bit time_t does not
        change the ABI.
      
      - As of commit c61eef72 ("drm: add support for monotonic vblank
        timestamps") in linux-3.8, the monotonic timestamp is the default
        and can only get reverted to wall-clock through a module-parameter.
      
      - With the default monotonic timestamps, there is no problem at all.
      
      - The drm_wait_vblank_ioctl() interface is alway safe on 64-bit
        architectures, on 32-bit it might overflow the 'long' timestamps
        in 2038 with wall-clock timestamps.
      
      - The event handling uses 'u32' seconds, which overflow in 2106
        on both 32-bit and 64-bit machines, when wall-clock timestamps
        are used.
      
      - The effect of overflowing either of the two is only temporary
        (during the overflow, and is likely to keep working again
        afterwards. It is likely the same problem as observing a
        'settimeofday()' call, which was the reason for moving to the
        monotonic timestamps in the first place.
      
      Overall, this seems good enough, so my patch removes the use of
      'timeval' from the vblank handling altogether and uses ktime_t
      consistently, except for the part where we copy the data to user
      space structures in the existing format.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Reviewed-by: NSean Paul <seanpaul@chromium.org>
      Reviewed-by: NKeith Packard <keithp@keithp.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      67680d3c
  2. 12 10月, 2017 11 次提交
  3. 11 10月, 2017 13 次提交
  4. 10 10月, 2017 5 次提交
  5. 09 10月, 2017 7 次提交