Skip to content

L
linux
Switch branch/tag
  1. 13 May, 2016 4 commits
  3. 12 May, 2016 3 commits
  5. 11 May, 2016 3 commits
  7. 10 May, 2016 15 commits
  9. 09 May, 2016 4 commits
    • Dave Airlie's avatar
      Merge tag 'v4.6-rc7' into drm-next · bafb86f5
      Dave Airlie authored 
      Merge this back as we've built up a fair few conflicts, and I have
some newer trees to pull in.
      bafb86f5
    • Dave Airlie's avatar
      drm/amdgpu: fix build on aarch64. · ba391646
      Dave Airlie authored 
      Same fix went in previously for some other files.
Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      ba391646
    • Dave Airlie's avatar
      Merge branch 'msm-next' of git://people.freedesktop.org/~robclark/linux into drm-next · 2c3d68ab
      Dave Airlie authored 
      Mostly cleanups, fixes, and 'struct fence' conversion this time
around, with one reservation patch which is a-b Sumit (which the fence
conversion patches depend on).

* 'msm-next' of git://people.freedesktop.org/~robclark/linux: (25 commits)
  drm/msm: Drop load/unload drm_driver ops
  drm/msm: Centralize connector registration/unregistration
  drm/msm/hdmi: Prevent gpio_free related kernel warnings
  drm/msm: print offender task name on hangcheck recovery
  drm/msm: fix leak in failed submit path
  drm/msm: de-indent submit_create()
  drm/msm: drop return from gpu->submit()
  drm/msm/mdp4: Don't manage DSI PLL regulators in MDP driver
  drm/msm/edp: Drop regulator_set_voltage call
  drm/msm/dsi: Fix regulator API abuse
  drm/msm: Move call to PTR_ERR_OR_ZERO after reassignment
  drm/msm/mdp: Add support for more RGBX formats
  drm: msm: remove unused variable
  drm/msm: fix ->last_fence() after recover
  drm/msm: 'struct fence' conversion
  drm/msm: remove fence_cbs
  drm/msm: introduce msm_fence_context
  drm/msm: split locking and pinning BO's
  drm/msm/gpu: simplify tracking in-flight bo's
  drm/msm: split out timeout_to_jiffies helper
  ...
      2c3d68ab
    • Dave Airlie's avatar
      Merge tag 'topic/drm-misc-2016-05-08' of git://anongit.freedesktop.org/drm-intel into drm-next · 2958cf0e
      Dave Airlie authored 
      Refcounting is hard, so here's a quick pull request with the one-liner to
fix up i915. Otherwise just a few other small things I picked up. Plus the
regression fix from Marten for rmfb behaviour that lingered around forever
since no testers. Feel free to cherry-pick that over to drm-fixes, but
given that there's not many who seemed to have cared, meh.

* tag 'topic/drm-misc-2016-05-08' of git://anongit.freedesktop.org/drm-intel:
  drm/i915: Correctly refcount connectors in hw state readou
  drm/panel: Flesh out kerneldoc
  drm: Add gpu.tmpl docbook to MAINTAINERS entry
  drm/core: Do not preserve framebuffer on rmfb, v4.
  drm: Fix up markup fumble
  drm/fb_helper: Fix a few typos
      2958cf0e
  11. 08 May, 2016 11 commits
    • Linus Torvalds's avatar
      Linux 4.6-rc7 · 44549e8f
      Linus Torvalds authored
      44549e8f
    • Archit Taneja's avatar
      drm/msm: Drop load/unload drm_driver ops · 2b669875
      Archit Taneja authored 
      The load/unload drm_driver ops are deprecated. They should be removed as
they result in creation of devices visible to userspace even before
the drm_device is registered.

Drop these ops and use drm_dev_alloc/register and drm_dev_unregister/unref
to explicitly create and destroy the drm device in the msm platform
driver's bind and unbind ops. With this in use, the drm connectors are
only registered once the drm_device is registered.

It also fixes the issue of stray debugfs files after the msm module is
removed. With this, all the debugfs files are removed, and allows
successive module insertions/removals.
Signed-off-by: default avatarArchit Taneja <architt@codeaurora.org>
      2b669875
    • Archit Taneja's avatar
      drm/msm: Centralize connector registration/unregistration · 8208ed93
      Archit Taneja authored 
      Move the drm_connector registration from the encoder(HDMI/DSI etc) drivers
to the msm platform driver. This will simplify the task of ensuring that
the connectors are registered only after the drm_device itself is
registered.

The connectors' destroy ops are made to use kzalloc instead of
devm_kzalloc to ensure that that the connectors can be successfully
unregistered when the msm driver module is removed. The memory for the
connectors is unallocated when drm_mode_config_cleanup() is called
during either during an error or during driver remove.
Signed-off-by: default avatarArchit Taneja <architt@codeaurora.org>
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      8208ed93
    • Archit Taneja's avatar
      drm/msm/hdmi: Prevent gpio_free related kernel warnings · c899f935
      Archit Taneja authored 
      Calling the legacy gpio_free on an invalid GPIO (a GPIO numbered -1)
results in kernel warnings. This causes a lot of backtraces when
we try to unload the drm/msm module.

Call gpio_free only on valid GPIOs.
Signed-off-by: default avatarArchit Taneja <architt@codeaurora.org>
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      c899f935
    • Rob Clark's avatar
      drm/msm: print offender task name on hangcheck recovery · 4816b626
      Rob Clark authored 
      Track the pid per submit, so we can print the name of the task which
submitted the batch that caused the gpu to hang.
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      4816b626
    • Rob Clark's avatar
      drm/msm: fix leak in failed submit path · 40e6815b
      Rob Clark authored 
      Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      40e6815b
    • Rob Clark's avatar
      drm/msm: de-indent submit_create() · 6860b56c
      Rob Clark authored 
      Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      6860b56c
    • Rob Clark's avatar
      drm/msm: drop return from gpu->submit() · 1193c3bc
      Rob Clark authored 
      At this point, there is nothing left to fail.  And submit already has a
fence assigned and is added to the submit_list.  Any problems from here
on out are asynchronous (ie. hangcheck/recovery).
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      1193c3bc
    • Archit Taneja's avatar
      drm/msm/mdp4: Don't manage DSI PLL regulators in MDP driver · ed19075b
      Archit Taneja authored 
      The MDP4 driver tries to request and set voltages for regulators required
by the DSI PLLs.

Firstly, the MDP4 driver shouldn't manage the DSI regulators, this should
be handled in the DSI driver. Secondly, it shouldn't try to set a fixed
voltage for regulators. Voltage constraints should be specified on the
regulator via DT and managed by the regulator core.

Remove all the DSI PLL regulator related code from the MDP4 driver. It's
managed in the DSI driver for MSM8960/APQ8064 already.
Signed-off-by: default avatarArchit Taneja <architt@codeaurora.org>
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      ed19075b
    • Archit Taneja's avatar
      drm/msm/edp: Drop regulator_set_voltage call · 1d15c165
      Archit Taneja authored 
      The eDP driver tries to set a fixed voltage for one of its regulators(vdda)
before enabling it. This shouldn't be done by the driver, the voltage
constraints should be specified on the regulator via DT and managed by
the regulator core. A driver should call regulator_set_voltage only if
it needs to change the voltage during runtime. Drop the
regulator_set_voltage call. Mention in a comment the voltage that the
regulator expects.
Signed-off-by: default avatarArchit Taneja <architt@codeaurora.org>
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      1d15c165
    • Archit Taneja's avatar
      drm/msm/dsi: Fix regulator API abuse · f377d597
      Archit Taneja authored 
      The voltage changing code in this driver is broken and should be
removed.  The driver sets a single, exact voltage on probe.  Unless
there is a very good reason for this (which should be documented in
comments) constraints like this need to be set via the machine
constraints, voltage setting in a driver is expected to be used in cases
where the voltage varies at runtime.

In addition client drivers should almost never be calling
regulator_can_set_voltage(), if the device needs to set a voltage it
needs to set the voltage and the regulator core will handle the case
where the regulator is fixed voltage.  If the driver simply skips
setting the voltage if it doesn't have permission then it should just
not bother in the first place.

Originally authored by Mark Brown <broonie@kernel.org>

Remove the min/max voltage data entries per SoC managed by the driver.
These aren't needed as we don't try to set voltages any more. Mention in
comments the voltages that each regulator expects.
Signed-off-by: default avatarArchit Taneja <architt@codeaurora.org>
Signed-off-by: default avatarRob Clark <robdclark@gmail.com>
      f377d597
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7