linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-arm-msm
	<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	freedreno
	<freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	dri-devel
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: [pull] drm/msm: drm-msm-fixes-2018-01-22 for 5.0
Date: Tue, 22 Jan 2019 17:53:31 -0500	[thread overview]
Message-ID: <CAF6AEGs9tqWOb3mVCqux5a2fH_0beW+5E8NsSCNSo=4+rn-MGg@mail.gmail.com> (raw)

Hi Dave,

A few fixes for v5.0.. the opp-level fix and removal of hard-coded irq
name is partially to make things smoother in v5.1 merge window to
avoid dependency on drm vs dt trees, but are otherwise sane changes.


The following changes since commit ba0ede185ef4c74bfecfe1c992be5dbcc5c5ac04:

  drm/msm/dpu: Fix clock issue after bind failure (2018-12-11 13:10:19 -0500)

are available in the Git repository at:

  git://people.freedesktop.org/~robclark/linux drm-msm-fixes-2018-01-22

for you to fetch changes up to fa3e64a16adcbad7c838589f0fbfb86abb24f5a0:

  drm/msm: avoid unused function warning (2019-01-22 11:32:10 -0500)

----------------------------------------------------------------
Arnd Bergmann (2):
      drm/msm/gpu: fix building without debugfs
      drm/msm: avoid unused function warning

Douglas Anderson (1):
      drm/msm: Fix A6XX support for opp-level

Joe Perches (1):
      drm/msm: Add __printf verification

Jordan Crouse (2):
      drm/msm/gpu: Remove hardcoded interrupt name
      drm/msm: drop interrupt-names

Kristian H. Kristensen (1):
      drm/msm: Unblock writer if reader closes file

Rob Clark (1):
      drm/msm: honor GPU_READONLY flag

 .../devicetree/bindings/display/msm/gpu.txt        |  1 -
 drivers/gpu/drm/msm/adreno/a6xx_gmu.c              |  2 +-
 drivers/gpu/drm/msm/adreno/adreno_gpu.c            |  1 -
 drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c          | 26 +++++++++++-----------
 drivers/gpu/drm/msm/msm_drv.h                      |  6 ++++-
 drivers/gpu/drm/msm/msm_gem.c                      |  8 +++++--
 drivers/gpu/drm/msm/msm_gem_vma.c                  |  5 +++--
 drivers/gpu/drm/msm/msm_gpu.c                      |  2 +-
 drivers/gpu/drm/msm/msm_gpu.h                      |  3 +--
 drivers/gpu/drm/msm/msm_rd.c                       |  7 +++++-
 10 files changed, 36 insertions(+), 25 deletions(-)
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno

                 reply	other threads:[~2019-01-22 22:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAF6AEGs9tqWOb3mVCqux5a2fH_0beW+5E8NsSCNSo=4+rn-MGg@mail.gmail.com' \
    --to=robdclark-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).