devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: display/msm: add core clock to the mdss bindings
Date: Mon, 9 Jan 2023 14:28:42 +0200	[thread overview]
Message-ID: <f5657c54-a27e-99d1-a996-ce1cefe46073@linaro.org> (raw)
In-Reply-To: <5a58eabc-08ba-57da-290d-b432f3f99268@linaro.org>

On 09/01/2023 12:51, Dmitry Baryshkov wrote:
> On 09/01/2023 12:35, Krzysztof Kozlowski wrote:
>> On 09/01/2023 01:52, Dmitry Baryshkov wrote:

[skipped]

>>
>> There were a lot, a lot of changes to MDSS/DPU bindings recently, so I
>> am really loosing track what is done where and when.
>>
>> There are also few separate patchsets from you on the lists. Could they
>> be combined into one cleanup?
> 
> Ack, I'll merge them into a single patchset.

I gave it some thought... Putting small non-mdss/mdp fixes aside, there 
are three series, which I'm trying to track:

- MDP5 schema conversion + per-SoC compatibles for MDP5 [1]
   no dependencies

- mdss/mdp/dpu -> display-subsystem, display-controller rename [2]
   depends on [1]

- mdp5 core clock support [3]
   depends on [1]

I think I'll target on merging [1] and [2] first, since they are purely 
DT + schema changes. If you prefer I can squash them for the next 
iteration or I can keep them separate.

For [3] I'll wait for first two to be in the proper shape, since it also 
contributes driver changes (and I don't want to have additional 
interlocks here).


[1] 
https://lore.kernel.org/linux-arm-msm/20230109050152.316606-1-dmitry.baryshkov@linaro.org/

[2] 
https://lore.kernel.org/linux-arm-msm/20230109051402.317577-1-dmitry.baryshkov@linaro.org/

[3] 
https://lore.kernel.org/linux-arm-msm/20230109005209.247356-1-dmitry.baryshkov@linaro.org/

-- 
With best wishes
Dmitry


  parent reply	other threads:[~2023-01-09 12:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  0:52 [PATCH v2 0/4] drm/msm/mdss: enable access to hw_rev from MDSS driver Dmitry Baryshkov
2023-01-09  0:52 ` [PATCH v2 1/4] dt-bindings: display/msm: add core clock to the mdss bindings Dmitry Baryshkov
2023-01-09 10:35   ` Krzysztof Kozlowski
2023-01-09 10:51     ` Dmitry Baryshkov
2023-01-09 11:20       ` Krzysztof Kozlowski
2023-01-09 12:06         ` Dmitry Baryshkov
2023-01-09 12:28       ` Dmitry Baryshkov [this message]
2023-01-09 14:30   ` Rob Herring
2023-01-09  0:52 ` [PATCH v2 2/4] drm/msm/mdss: enable optional core clock for MDP5 MDSS Dmitry Baryshkov
2023-01-09  0:52 ` [PATCH v2 3/4] drm/msm/mdss: check for core clk before accessing HW_REV Dmitry Baryshkov
2023-01-09  0:52 ` [PATCH v2 4/4] drm/msm/mdss: move is_mdp5 condition to msm_mdss_init 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=f5657c54-a27e-99d1-a996-ce1cefe46073@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@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).