linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
	robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org
Subject: [PATCH RESEND 00/10]  drm/msm: A handful of dpu fixes
Date: Wed, 21 Feb 2018 09:55:24 -0500	[thread overview]
Message-ID: <20180221145534.219625-1-seanpaul@chromium.org> (raw)

[RESEND b/c lists.fdo was out of memory]

We've finally got the mtp development kit booting the DPU driver that
was sent upstream last week. Here are some of the patches that were
necessary to do that. There are a bunch more, but they touch downstream
code that is not going upstream (namely dsi-staging and smmu). The
booting kernel can be found at [1].

Once the patches in this series receive some light review, I'll drop
them on for-next at [2].

Thanks,

Sean

[1]- https://cgit.freedesktop.org/~seanpaul/dpu-staging/log/?h=mtp-testing
[2]- https://cgit.freedesktop.org/~seanpaul/dpu-staging/log/?h=for-next

*** BLURB HERE ***

Jeykumar Sankaran (1):
  drm/msm/dpu: Fix writeback compile macros

Sean Paul (9):
  drm/msm: Add displayport files to Makefile
  drm/msm: Include the dpu_dbg header in msm_drv.c
  drm/msm: Change driver name back to msm
  drm/msm: Remove smmu driver init/cleanup from msm_drv
  drm/msm: Defer probe if display component not found
  drm/msm: Fix deadlock calling msm_gem_new()
  drm/msm: Populate kms->irq for dpu
  drm/msm: Sprinkle pm_runtime calls around
  drm/msm: Restore msm_atomic_check hook

 drivers/gpu/drm/msm/Makefile                  | 14 ++++++++++++++
 drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c      |  3 +++
 drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c   |  7 ++-----
 .../gpu/drm/msm/disp/dpu1/dpu_hw_reg_dma_v1.c |  2 --
 drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c       | 19 ++++++++++++++++++-
 drivers/gpu/drm/msm/msm_drv.c                 | 17 +++++++++--------
 6 files changed, 46 insertions(+), 16 deletions(-)

-- 
2.16.1.291.g4437f3f132-goog

_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno

             reply	other threads:[~2018-02-21 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 14:55 Sean Paul [this message]
     [not found] ` <20180221145534.219625-1-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-02-21 14:55   ` [PATCH RESEND 01/10] drm/msm: Add displayport files to Makefile Sean Paul
2018-02-21 14:55   ` [PATCH RESEND 02/10] drm/msm: Include the dpu_dbg header in msm_drv.c Sean Paul
  -- strict thread matches above, loose matches on Subject: below --
2018-02-21 15:18 [PATCH RESEND 00/10] drm/msm: A handful of dpu fixes Sean Paul

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=20180221145534.219625-1-seanpaul@chromium.org \
    --to=seanpaul-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
    --cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@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).