From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Krishna Manikandan <quic_mkrishn@quicinc.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>
Subject: Re: [PATCH 08/11] dt-bindings: display/msm: add mdp-opp-table to dpu-sdm845
Date: Mon, 27 Jun 2022 12:05:06 -0600 [thread overview]
Message-ID: <20220627180506.GA2679395-robh@kernel.org> (raw)
In-Reply-To: <20220625232513.522599-9-dmitry.baryshkov@linaro.org>
On Sun, Jun 26, 2022 at 02:25:10AM +0300, Dmitry Baryshkov wrote:
> On SDM845 platforms DPU device tree node contains child object
> mdp-opp-table providing OPP table for the DPU. Add it to the list of
> properties to let sdm845.dtsi to validate.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> .../devicetree/bindings/display/msm/dpu-sdm845.yaml | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/msm/dpu-sdm845.yaml b/Documentation/devicetree/bindings/display/msm/dpu-sdm845.yaml
> index 0dc16326bf8e..cc95adcf8f11 100644
> --- a/Documentation/devicetree/bindings/display/msm/dpu-sdm845.yaml
> +++ b/Documentation/devicetree/bindings/display/msm/dpu-sdm845.yaml
> @@ -50,6 +50,10 @@ properties:
> maxItems: 1
>
> operating-points-v2: true
> +
> + mdp-opp-table:
Is there another kind of opp-table besides mdp? Node names should be
generic.
> + $ref: /schemas/opp/opp-v2.yaml#
> +
> ports:
> $ref: /schemas/graph.yaml#/properties/ports
> description: |
> @@ -116,11 +120,12 @@ examples:
> <0x0aeb0000 0x2008>;
> reg-names = "mdp", "vbif";
>
> - clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
> + clocks = <&gcc GCC_DISP_AXI_CLK>,
> + <&dispcc DISP_CC_MDSS_AHB_CLK>,
What does the OPP table have to do with clocks? Adding a clock anywhere
but the end is an ABI break.
> <&dispcc DISP_CC_MDSS_AXI_CLK>,
> <&dispcc DISP_CC_MDSS_MDP_CLK>,
> <&dispcc DISP_CC_MDSS_VSYNC_CLK>;
> - clock-names = "iface", "bus", "core", "vsync";
> + clock-names = "gcc-bus", "iface", "bus", "core", "vsync";
>
> interrupt-parent = <&mdss>;
> interrupts = <0>;
> --
> 2.35.1
>
>
next prev parent reply other threads:[~2022-06-27 18:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 23:25 [PATCH 00/11] dt-bindings: display/msm: rework MDSS and DPU bindings Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 01/11] dt-bindings: display/msm: split qcom, mdss bindings Dmitry Baryshkov
2022-06-30 22:52 ` Rob Herring
2022-07-05 16:41 ` Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 02/11] dt-bindings: display/msm: move qcom,sdm845-mdss schema to mdss.yaml Dmitry Baryshkov
2022-06-28 14:38 ` Rob Herring
2022-06-28 20:28 ` Dmitry Baryshkov
2022-06-30 23:02 ` Rob Herring
2022-06-25 23:25 ` [PATCH 03/11] dt-bindings: display/msm: move qcom,sc7180-mdss " Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 04/11] dt-bindings: display/msm: move qcom,sc7280-mdss " Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 05/11] dt-bindings: display/msm: move qcom,qcm2290-mdss " Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 06/11] dt-bindings: display/msm: move qcom,msm8998-mdss " Dmitry Baryshkov
2022-06-30 23:05 ` Rob Herring
2022-06-25 23:25 ` [PATCH 07/11] dt-bindings: display/mdm: add gcc-bus clock to dpu-smd845 Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 08/11] dt-bindings: display/msm: add mdp-opp-table to dpu-sdm845 Dmitry Baryshkov
2022-06-27 18:05 ` Rob Herring [this message]
2022-06-28 20:23 ` Dmitry Baryshkov
2022-06-29 9:23 ` Krzysztof Kozlowski
2022-06-29 18:57 ` Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 09/11] dt-bindings: display/msm: add mdp-opp-table to dpu-sc7180 Dmitry Baryshkov
2022-06-25 23:25 ` [PATCH 10/11] dt-bindings: display/msm: add opp-table to dpu-sc7280 Dmitry Baryshkov
2022-06-30 23:06 ` Rob Herring
2022-06-25 23:25 ` [PATCH 11/11] dt-bindings: display/msm: move common DPU properties to dpu-common.yaml Dmitry Baryshkov
2022-06-30 23:11 ` Rob Herring
2022-07-08 9:14 ` Dmitry Baryshkov
2022-07-12 20:47 ` Rob Herring
2022-07-12 21:41 ` 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=20220627180506.GA2679395-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_mkrishn@quicinc.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).