From: Adam Skladowski <a39.skl@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Adam Skladowski <a39.skl@gmail.com>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kalyan Thota <quic_kalyant@quicinc.com>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Loic Poulain <loic.poulain@linaro.org>,
Adam Skladowski <a_skl39@protonmail.com>,
Stephen Boyd <swboyd@chromium.org>,
Jason Wang <wangborong@cdjrlc.com>,
Vinod Polimera <quic_vpolimer@quicinc.com>,
Vinod Koul <vkoul@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Add SM6115 MDSS/DPU support
Date: Sun, 20 Nov 2022 14:37:35 +0100 [thread overview]
Message-ID: <20221120133744.24808-1-a39.skl@gmail.com> (raw)
This patch series add support for MDSS and DPU block found on SM6115.
These patches were tested on Xiaomi Redmi 9T smartphone.
Adam Skladowski (2):
dt-bindings: display/msm: add support for the display on SM6115
drm/msm/disp/dpu1: add support for display on SM6115
.../bindings/display/msm/qcom,sm6115-dpu.yaml | 87 ++++++++
.../display/msm/qcom,sm6115-mdss.yaml | 187 ++++++++++++++++++
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 87 ++++++++
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 1 +
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 1 +
drivers/gpu/drm/msm/msm_mdss.c | 5 +
6 files changed, 368 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,sm6115-dpu.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,sm6115-mdss.yaml
--
2.25.1
next reply other threads:[~2022-11-20 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 13:37 Adam Skladowski [this message]
2022-11-20 13:37 ` [PATCH 1/2] dt-bindings: display/msm: add support for the display Adam Skladowski
2022-11-20 15:09 ` Rob Herring
2022-11-20 15:41 ` Rob Herring
2022-11-22 23:44 ` Dmitry Baryshkov
2022-11-23 23:11 ` Dmitry Baryshkov
2022-11-20 13:37 ` [PATCH 2/2] drm/msm/disp/dpu1: add support for display on SM6115 Adam Skladowski
2022-11-22 23:54 ` Dmitry Baryshkov
2022-11-23 21:05 ` Dmitry Baryshkov
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=20221120133744.24808-1-a39.skl@gmail.com \
--to=a39.skl@gmail.com \
--cc=a_skl39@protonmail.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_kalyant@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@kernel.org \
--cc=wangborong@cdjrlc.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).