linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Schwalm <maxim.schwalm@gmail.com>
To: Rob Herring <robh@kernel.org>, 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>,
	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: Tue, 5 Sep 2023 22:23:16 +0200	[thread overview]
Message-ID: <755a2be4-6947-d756-2eee-0ba14086d781@gmail.com> (raw)
In-Reply-To: <20230821161441.GA1743870-robh@kernel.org>

Hi Rob,

On 21.08.23 18:14, Rob Herring wrote:
> 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.

currently, just bus-width is used in devicetrees, but I don't think that
it is needed at the moment. So perhaps the property can be dropped.

>> +                  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.

The reason for adding this was that just one of them can be utilized at
the same time. Having both could potentially break the display output.
I think that all the other nvidia,* properties could marked as
deprecated as well because they don't seem to be doing much since commit
d9f980ebcd01 ("drm/tegra: output: rgb: Wrap directly-connected panel
into DRM bridge").

>> +
>> +          additionalProperties: false
> 
> Move this up too.
> 

Best regards,
Maxim

  reply	other threads:[~2023-09-05 20:23 UTC|newest]

Thread overview: 9+ 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 ` [PATCH v3 1/5] ARM: dts: tegra: Drop unit-address from parallel RGB output port 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-21 16:14   ` Rob Herring
2023-09-05 20:23     ` Maxim Schwalm [this message]
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 4/5] drm/tegra: output: hdmi: Support bridge/connector Svyatoslav Ryhel
2023-08-07 14:35 ` [PATCH v3 5/5] ARM: tegra: transformers: add connector node Svyatoslav Ryhel
2023-10-10 15:46 ` (subset) [PATCH v3 0/5] Support bridge/connector by Tegra HDMI 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=755a2be4-6947-d756-2eee-0ba14086d781@gmail.com \
    --to=maxim.schwalm@gmail.com \
    --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=mperttunen@nvidia.com \
    --cc=robh@kernel.org \
    --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 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).