From: Rob Herring <robh@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
Dmitry Osipenko <digetx@gmail.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/5] dt-bindings: display: tegra: nvidia,tegra20-dc: Add parallel RGB output port node
Date: Mon, 21 Aug 2023 11:14:41 -0500 [thread overview]
Message-ID: <20230821161441.GA1743870-robh@kernel.org> (raw)
In-Reply-To: <20230807143515.7882-3-clamor95@gmail.com>
On Mon, Aug 07, 2023 at 05:35:12PM +0300, Svyatoslav Ryhel wrote:
> From: Maxim Schwalm <maxim.schwalm@gmail.com>
>
> Either this node, which is optional, or the nvidia,panel property can be
> present.
>
> Signed-off-by: Maxim Schwalm <maxim.schwalm@gmail.com>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> .../display/tegra/nvidia,tegra20-dc.yaml | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
> index 69be95afd562..102304703062 100644
> --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
> +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
> @@ -127,6 +127,37 @@ allOf:
> $ref: /schemas/types.yaml#/definitions/phandle
> description: phandle of a display panel
>
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + description: Parallel RGB output port
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
Just to make sure, what properties are you using from this? Usually
we'll list them though not a hard requirement. If none, then you just
need to ref graph.yaml#/properties/port instead and can drop the rest.
> + unevaluatedProperties: false
> +
> + unevaluatedProperties: false
In the indented cases, it's easier to read if this is before
properties/patternProperties.
> +
> + anyOf:
> + - if:
> + not:
> + properties:
> + nvidia,panel: false
> + then:
> + not:
> + properties:
> + port: true
> + - if:
> + not:
> + properties:
> + port: false
> + then:
> + not:
> + properties:
> + nvidia,panel: true
I would prefer to drop this and mark "nvidia,panel" as deprecated.
Eventually I plan to add a mode to the tools to warn on using deprecated
properties. Having both could be perfectly fine too. You have the
"nvidia,panel" for compatibility with an old OS version and 'port' to
work with newer users.
> +
> + additionalProperties: false
Move this up too.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Jonathan Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-tegra@vger.kernel.org, Dmitry Osipenko <digetx@gmail.com>,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: Re: [PATCH v3 2/5] dt-bindings: display: tegra: nvidia,tegra20-dc: Add parallel RGB output port node
Date: Mon, 21 Aug 2023 11:14:41 -0500 [thread overview]
Message-ID: <20230821161441.GA1743870-robh@kernel.org> (raw)
In-Reply-To: <20230807143515.7882-3-clamor95@gmail.com>
On Mon, Aug 07, 2023 at 05:35:12PM +0300, Svyatoslav Ryhel wrote:
> From: Maxim Schwalm <maxim.schwalm@gmail.com>
>
> Either this node, which is optional, or the nvidia,panel property can be
> present.
>
> Signed-off-by: Maxim Schwalm <maxim.schwalm@gmail.com>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> .../display/tegra/nvidia,tegra20-dc.yaml | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
> index 69be95afd562..102304703062 100644
> --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
> +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
> @@ -127,6 +127,37 @@ allOf:
> $ref: /schemas/types.yaml#/definitions/phandle
> description: phandle of a display panel
>
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + description: Parallel RGB output port
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
Just to make sure, what properties are you using from this? Usually
we'll list them though not a hard requirement. If none, then you just
need to ref graph.yaml#/properties/port instead and can drop the rest.
> + unevaluatedProperties: false
> +
> + unevaluatedProperties: false
In the indented cases, it's easier to read if this is before
properties/patternProperties.
> +
> + anyOf:
> + - if:
> + not:
> + properties:
> + nvidia,panel: false
> + then:
> + not:
> + properties:
> + port: true
> + - if:
> + not:
> + properties:
> + port: false
> + then:
> + not:
> + properties:
> + nvidia,panel: true
I would prefer to drop this and mark "nvidia,panel" as deprecated.
Eventually I plan to add a mode to the tools to warn on using deprecated
properties. Having both could be perfectly fine too. You have the
"nvidia,panel" for compatibility with an old OS version and 'port' to
work with newer users.
> +
> + additionalProperties: false
Move this up too.
Rob
next prev parent reply other threads:[~2023-08-21 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:35 [PATCH v3 0/5] Support bridge/connector by Tegra HDMI Svyatoslav Ryhel
2023-08-07 14:35 ` Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 1/5] ARM: dts: tegra: Drop unit-address from parallel RGB output port Svyatoslav Ryhel
2023-08-07 14:35 ` Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 2/5] dt-bindings: display: tegra: nvidia,tegra20-dc: Add parallel RGB output port node Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 2/5] dt-bindings: display: tegra: nvidia, tegra20-dc: " Svyatoslav Ryhel
2023-08-21 16:14 ` Rob Herring [this message]
2023-08-21 16:14 ` [PATCH v3 2/5] dt-bindings: display: tegra: nvidia,tegra20-dc: " Rob Herring
2023-09-05 20:23 ` Maxim Schwalm
2023-09-05 20:23 ` Maxim Schwalm
2023-08-07 14:35 ` [PATCH v3 3/5] dt-bindings: display: tegra: nvidia,tegra20-hdmi: Add HDMI " Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 3/5] dt-bindings: display: tegra: nvidia, tegra20-hdmi: " Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 4/5] drm/tegra: output: hdmi: Support bridge/connector Svyatoslav Ryhel
2023-08-07 14:35 ` Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 5/5] ARM: tegra: transformers: add connector node Svyatoslav Ryhel
2023-08-07 14:35 ` Svyatoslav Ryhel
2023-10-10 15:46 ` (subset) [PATCH v3 0/5] Support bridge/connector by Tegra HDMI Thierry Reding
2023-10-10 15:46 ` Thierry Reding
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=20230821161441.GA1743870-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maxim.schwalm@gmail.com \
--cc=mperttunen@nvidia.com \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.