From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Rob Clark <robdclark@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Mahadevan <quic_mahap@quicinc.com>
Cc: 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: Re: [PATCH 3/4] dt-bindings: display/msm: add stream 1 pixel clock binding
Date: Tue, 3 Dec 2024 09:04:39 +0100 [thread overview]
Message-ID: <39f8e20a-e8c3-4625-abb1-9f35f416705d@kernel.org> (raw)
In-Reply-To: <20241202-dp_mst_bindings-v1-3-9a9a43b0624a@quicinc.com>
On 03/12/2024 04:31, Abhinav Kumar wrote:
> On some chipsets the display port controller can support more
Which chipsets?
> than one pixel stream (multi-stream transport). To support MST
> on such chipsets, add the binding for stream 1 pixel clock for
> display port controller. Since this mode is not supported on all
> chipsets, add exception rules and min/max items to clearly mark
> which chipsets support only SST mode (single stream) and which ones
> support MST.
>
> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> ---
> .../bindings/display/msm/dp-controller.yaml | 32 ++++++++++++++++++++++
> .../bindings/display/msm/qcom,sa8775p-mdss.yaml | 9 ++++--
> 2 files changed, 38 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/msm/dp-controller.yaml b/Documentation/devicetree/bindings/display/msm/dp-controller.yaml
> index 9fe2bf0484d8..650d19e58277 100644
> --- a/Documentation/devicetree/bindings/display/msm/dp-controller.yaml
> +++ b/Documentation/devicetree/bindings/display/msm/dp-controller.yaml
> @@ -50,30 +50,38 @@ properties:
> maxItems: 1
>
> clocks:
> + minItems: 5
> items:
> - description: AHB clock to enable register access
> - description: Display Port AUX clock
> - description: Display Port Link clock
> - description: Link interface clock between DP and PHY
> - description: Display Port stream 0 Pixel clock
> + - description: Display Port stream 1 Pixel clock
>
> clock-names:
> + minItems: 5
> items:
> - const: core_iface
> - const: core_aux
> - const: ctrl_link
> - const: ctrl_link_iface
> - const: stream_pixel
> + - const: stream_1_pixel
>
> assigned-clocks:
> + minItems: 2
> items:
> - description: link clock source
> - description: stream 0 pixel clock source
> + - description: stream 1 pixel clock source
>
> assigned-clock-parents:
> + minItems: 2
> items:
> - description: Link clock PLL output provided by PHY block
> - description: Stream 0 pixel clock PLL output provided by PHY block
> + - description: Stream 1 pixel clock PLL output provided by PHY block
>
> phys:
> maxItems: 1
> @@ -175,6 +183,30 @@ allOf:
> required:
> - "#sound-dai-cells"
>
Missing if: narrowing this to 5 items for other devices.
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,sa8775p-dp
> +
> + then:
> + properties:
> + clocks:
Missing minItems, otherwise it is pointless.
> + maxItems: 6
> + clock-names:
> + items:
> + - const: core_iface
> + - const: core_aux
> + - const: ctrl_link
> + - const: ctrl_link_iface
> + - const: stream_pixel
> + - const: stream_1_pixel
> + assigned-clocks:
> + maxItems: 3
Missing minItems... or just drop, it's not accurate or not even correct.
I can assign 4 clocks, why not? Or rather: why do you stop users from
assigning 4 clocks?
> + assigned-clock-parents:
> + maxItems: 3
> +
> additionalProperties: false
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-03 8:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 3:31 [PATCH 0/4] dt-bindings: msm/dp: add support for pixel clock to driver another stream Abhinav Kumar
2024-12-03 3:31 ` [PATCH 1/4] dt-bindings: display: msm: dp-controller: document pixel clock stream Abhinav Kumar
2024-12-03 8:01 ` Krzysztof Kozlowski
2025-04-23 2:23 ` Abhinav Kumar
2024-12-03 3:31 ` [PATCH 2/4] dt-bindings: display: msm: dp-controller: document clock parents better Abhinav Kumar
2024-12-03 8:01 ` Krzysztof Kozlowski
2024-12-03 13:41 ` Dmitry Baryshkov
2024-12-04 8:02 ` Krzysztof Kozlowski
2024-12-04 10:09 ` Dmitry Baryshkov
2024-12-05 7:33 ` Krzysztof Kozlowski
2024-12-05 11:32 ` Dmitry Baryshkov
2025-04-23 2:40 ` Abhinav Kumar
2024-12-03 3:31 ` [PATCH 3/4] dt-bindings: display/msm: add stream 1 pixel clock binding Abhinav Kumar
2024-12-03 8:04 ` Krzysztof Kozlowski [this message]
2025-04-23 2:46 ` Abhinav Kumar
2025-05-08 6:18 ` Krzysztof Kozlowski
2025-05-22 0:49 ` Abhinav Kumar
2024-12-03 13:43 ` Dmitry Baryshkov
2025-04-23 2:46 ` Abhinav Kumar
2025-04-23 14:23 ` Dmitry Baryshkov
2025-05-22 0:48 ` Abhinav Kumar
2024-12-03 3:31 ` [PATCH 4/4] dt-bindings: display: msm: dp: update maintainer entry Abhinav Kumar
2024-12-10 9:24 ` Krzysztof Kozlowski
2024-12-10 22:21 ` [PATCH 0/4] dt-bindings: msm/dp: add support for pixel clock to driver another stream Marijn Suijten
2024-12-24 20: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=39f8e20a-e8c3-4625-abb1-9f35f416705d@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_mahap@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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