From: Kalyan Thota <kalyan_t@codeaurora.org>
To: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org
Cc: Kalyan Thota <kalyan_t@codeaurora.org>,
linux-kernel@vger.kernel.org, robdclark@gmail.com,
seanpaul@chromium.org, hoegsberg@chromium.org,
dhar@codeaurora.org, jsanka@codeaurora.org,
chandanu@codeaurora.org, travitej@codeaurora.org,
nganji@codeaurora.org
Subject: [PATCH 0/4] Add support for SC7180 display
Date: Mon, 25 Nov 2019 17:29:25 +0530 [thread overview]
Message-ID: <1574683169-19342-1-git-send-email-kalyan_t@codeaurora.org> (raw)
SC7180 follows a newer architecture where in some flush controls have been re-organized to simplify programming and provide for future expandability.
Specifically:
1) The TIMING_<j> bits that control flush of INTF_<j> have been replaced with a common INTF flush bit which flushes the programming in the MDP_CTL_<id>_INTF_ACTIVE register
2) Individual flush bits for MERGE_3D, DSC and CDWN have been added which flush the programming in the MDP_CTL_<id>_MERGE_3D_ACTIVE, ... etc respectively
3) PERIPH flush bit has been added to flush DSP packets for DisplayPort
The complete datapath is described using the MDP_CTL_<id>_TOP and newly added ACTIVE registers to handle other sub blocks
such as interface (INTF) resources, PingPong buffer / Layer Mixer, Display Stream Compression (DSC) resources, writeback (WB) and 3D Merge
selections that are part of the datapath.
Kalyan Thota (4):
dt-bindings: msm:disp: add sc7180 DPU variant
msm:disp:dpu1: add support for display for SC7180 target
msm:disp:dpu1: setup display datapath for SC7180 target
msm:disp:dpu1: add mixer selection for display topology
.../devicetree/bindings/display/msm/dpu.txt | 4 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 21 ++-
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 21 ++-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 191 +++++++++++++++++++--
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 6 +
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.c | 84 ++++++++-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.h | 24 +++
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_intf.c | 28 +++
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_intf.h | 6 +
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c | 3 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 1 +
drivers/gpu/drm/msm/msm_drv.c | 4 +-
12 files changed, 370 insertions(+), 23 deletions(-)
--
1.9.1
next reply other threads:[~2019-11-25 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 11:59 Kalyan Thota [this message]
2019-11-25 11:59 ` [PATCH 1/4] dt-bindings: msm:disp: add sc7180 DPU variant Kalyan Thota
2019-12-05 18:18 ` Rob Herring
2019-11-25 11:59 ` [PATCH 2/4] msm:disp:dpu1: add support for display for SC7180 target Kalyan Thota
2019-11-25 11:59 ` [PATCH 3/4] msm:disp:dpu1: setup display datapath " Kalyan Thota
2019-11-25 11:59 ` [PATCH 4/4] msm:disp:dpu1: add mixer selection for display topology Kalyan Thota
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=1574683169-19342-1-git-send-email-kalyan_t@codeaurora.org \
--to=kalyan_t@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dhar@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hoegsberg@chromium.org \
--cc=jsanka@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nganji@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
--cc=travitej@codeaurora.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).