linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: robdclark@gmail.com
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Archit Taneja <architt@codeaurora.org>
Subject: [PATCH v2 0/7] drm/msm: Misc patches
Date: Thu, 25 Feb 2016 11:19:41 +0530	[thread overview]
Message-ID: <1456379388-14767-1-git-send-email-architt@codeaurora.org> (raw)

These are mainly small fixes in drm/msm. The last patch adds a way to
parse DSI lanes information via DT.

Changes in v2:
- Updated the patch VDD regulator patch for MSM8916. After studying
  schematics and looking at DSI specs again carefully, we realized
  that the vdd supply is meant for the panels that connect to the
  dsi host. The downstream driver controlled it within the DSI
  driver itself, which led to the confusion.
- Updated the DT bindings for parsing DSI data lanes
- Added a patch to constify iommu port names
- Fixed some checkpatch warnings.

Archit Taneja (5):
  drm/msm/mdp: Use atomic helper to set crtc property
  drm/msm: Free fb helper resources in msm_unload
  drm/msm/dsi: Remove incorrect warning on host attach
  drm/msm/dsi: Drop VDD regulator for MSM8916
  drm/msm/dsi: Parse DSI lanes via DT

Rob Clark (1):
  drm/msm: make iommu port names const'ier

Sricharan R (1):
  drm/msm/mdp: Detach iommu in mdp4_destroy

 .../devicetree/bindings/display/msm/dsi.txt        |  32 +++++-
 drivers/gpu/drm/msm/dsi/dsi_cfg.c                  |   3 +-
 drivers/gpu/drm/msm/dsi/dsi_host.c                 | 118 +++++++++++++++++----
 drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.c           |   9 +-
 drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c            |  17 ++-
 drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.h            |   1 +
 drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc.c           |   9 +-
 drivers/gpu/drm/msm/msm_drv.c                      |   5 +
 drivers/gpu/drm/msm/msm_drv.h                      |   1 +
 drivers/gpu/drm/msm/msm_iommu.c                    |   6 +-
 drivers/gpu/drm/msm/msm_mmu.h                      |   4 +-
 11 files changed, 154 insertions(+), 51 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

             reply	other threads:[~2016-02-25  5:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25  5:49 Archit Taneja [this message]
2016-02-25  5:49 ` [PATCH v2 1/7] drm/msm/mdp: Use atomic helper to set crtc property Archit Taneja
2016-02-25  5:49 ` [PATCH v2 2/7] drm/msm: make iommu port names const'ier Archit Taneja
2016-02-25  5:49 ` [PATCH v2 3/7] drm/msm/mdp: Detach iommu in mdp4_destroy Archit Taneja
2016-02-25  5:49 ` [PATCH v2 4/7] drm/msm: Free fb helper resources in msm_unload Archit Taneja
2016-02-25  5:49 ` [PATCH v2 5/7] drm/msm/dsi: Remove incorrect warning on host attach Archit Taneja
2016-02-25  5:49 ` [PATCH v2 6/7] drm/msm/dsi: Drop VDD regulator for MSM8916 Archit Taneja
2016-02-25  5:49 ` [PATCH v2 7/7] drm/msm/dsi: Parse DSI lanes via DT Archit Taneja
2016-03-02 17:37   ` Rob Herring

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=1456379388-14767-1-git-send-email-architt@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robdclark@gmail.com \
    /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).