From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.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,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
Rob Herring <robh@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
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>,
Krishna Manikandan <quic_mkrishn@quicinc.com>
Subject: Re: [PATCH v5 00/12] SM63(50|75) DPU support
Date: Thu, 1 Jun 2023 03:16:52 +0300 [thread overview]
Message-ID: <0fbe5ddb-c3de-0724-fb69-a99e4980b26c@linaro.org> (raw)
In-Reply-To: <20230411-topic-straitlagoon_mdss-v5-0-998b4d2f7dd1@linaro.org>
On 23/05/2023 10:46, Konrad Dybcio wrote:
[skipped the changelog]
> ---
> Konrad Dybcio (12):
> dt-bindings: display/msm: dsi-controller-main: Add SM6350
> dt-bindings: display/msm: dsi-controller-main: Add SM6375
> dt-bindings: display/msm: sc7180-dpu: Describe SM6350 and SM6375
> dt-bindings: display/msm: Add SM6350 MDSS
> dt-bindings: display/msm: Add SM6375 MDSS
> drm/msm/dpu: Add SM6350 support
> drm/msm: mdss: Add SM6350 support
> drm/msm/dpu: Add SM6375 support
> drm/msm: mdss: Add SM6375 support
> iommu/arm-smmu-qcom: Sort the compatible list alphabetically
> iommu/arm-smmu-qcom: Add SM6375 DPU compatible
> iommu/arm-smmu-qcom: Add SM6350 DPU compatible
As we are now nearly ready to merge this series, Will, Robin, what
should be the merge strategy for these three patches? Would you take
them through the arm-smmu/iommu tree?
>
> .../bindings/display/msm/dsi-controller-main.yaml | 4 +
> .../bindings/display/msm/qcom,sc7180-dpu.yaml | 23 ++-
> .../bindings/display/msm/qcom,sm6350-mdss.yaml | 214 ++++++++++++++++++++
> .../bindings/display/msm/qcom,sm6375-mdss.yaml | 216 +++++++++++++++++++++
> .../gpu/drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h | 173 +++++++++++++++++
> .../gpu/drm/msm/disp/dpu1/catalog/dpu_6_9_sm6375.h | 139 +++++++++++++
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 6 +
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 2 +
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 2 +
> drivers/gpu/drm/msm/msm_mdss.c | 10 +
> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 6 +-
> 11 files changed, 792 insertions(+), 3 deletions(-)
> ---
> base-commit: 9f925874281f7e8855855d6210d6e29d844e4307
> change-id: 20230411-topic-straitlagoon_mdss-8f34cacd5e26
>
> Best regards,
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-06-01 0:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 7:46 [PATCH v5 00/12] SM63(50|75) DPU support Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 01/12] dt-bindings: display/msm: dsi-controller-main: Add SM6350 Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 02/12] dt-bindings: display/msm: dsi-controller-main: Add SM6375 Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 03/12] dt-bindings: display/msm: sc7180-dpu: Describe SM6350 and SM6375 Konrad Dybcio
2023-06-04 17:57 ` Krzysztof Kozlowski
2023-05-23 7:46 ` [PATCH v5 04/12] dt-bindings: display/msm: Add SM6350 MDSS Konrad Dybcio
2023-05-23 8:34 ` Rob Herring
2023-06-01 0:12 ` Dmitry Baryshkov
2023-06-04 18:04 ` Krzysztof Kozlowski
2023-05-23 7:46 ` [PATCH v5 05/12] dt-bindings: display/msm: Add SM6375 MDSS Konrad Dybcio
2023-05-23 8:34 ` Rob Herring
2023-06-04 18:04 ` Krzysztof Kozlowski
2023-06-05 17:01 ` Konrad Dybcio
2023-06-05 17:09 ` Dmitry Baryshkov
2023-05-23 7:46 ` [PATCH v5 06/12] drm/msm/dpu: Add SM6350 support Konrad Dybcio
2023-05-23 14:39 ` Dmitry Baryshkov
2023-05-23 7:46 ` [PATCH v5 07/12] drm/msm: mdss: " Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 08/12] drm/msm/dpu: Add SM6375 support Konrad Dybcio
2023-06-01 14:56 ` Marijn Suijten
2023-06-02 8:56 ` Konrad Dybcio
2023-06-04 18:23 ` Marijn Suijten
2023-05-23 7:46 ` [PATCH v5 09/12] drm/msm: mdss: " Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 10/12] iommu/arm-smmu-qcom: Sort the compatible list alphabetically Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 11/12] iommu/arm-smmu-qcom: Add SM6375 DPU compatible Konrad Dybcio
2023-05-23 7:46 ` [PATCH v5 12/12] iommu/arm-smmu-qcom: Add SM6350 " Konrad Dybcio
2023-06-01 0:16 ` Dmitry Baryshkov [this message]
2023-06-05 15:43 ` [PATCH v5 00/12] SM63(50|75) DPU support Will Deacon
2023-06-05 15:50 ` 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=0fbe5ddb-c3de-0724-fb69-a99e4980b26c@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_mkrishn@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sean@poorly.run \
--cc=will@kernel.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).