From: Rob Herring <robh@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: 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>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: display: tegra: document Tegra20 HDMI port
Date: Tue, 10 Feb 2026 08:19:17 -0600 [thread overview]
Message-ID: <20260210141917.GA2659856-robh@kernel.org> (raw)
In-Reply-To: <20260210094908.14276-2-clamor95@gmail.com>
On Tue, Feb 10, 2026 at 11:49:07AM +0200, Svyatoslav Ryhel wrote:
> Tegra HDMI can be modeled using an OF graph. Reflect this in the bindings.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> .../bindings/display/tegra/nvidia,tegra20-hdmi.yaml | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml
> index f77197e4869f..f33b700bf0ee 100644
> --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml
> +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml
> @@ -82,6 +82,10 @@ properties:
> description: phandle of a display panel
> $ref: /schemas/types.yaml#/definitions/phandle
>
> + port:
> + description: connection to controller receiving HDMI signals
Describe this in terms of this block, not what it is connected to. It
could be an hdmi-connector node or a bridge.
> + $ref: /schemas/graph.yaml#/properties/port
> +
> "#sound-dai-cells":
> const: 0
>
> @@ -97,8 +101,13 @@ required:
> - reset-names
> - pll-supply
> - vdd-supply
> - - nvidia,ddc-i2c-bus
> - - nvidia,hpd-gpio
> +
> +anyOf:
> + - required:
> + - nvidia,ddc-i2c-bus
> + - nvidia,hpd-gpio
> + - required:
> + - port
>
> examples:
> - |
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-02-10 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 9:49 [PATCH v1 0/2] ARM: tegra: document Tegra20 HDMI port Svyatoslav Ryhel
2026-02-10 9:49 ` [PATCH v1 1/2] dt-bindings: display: " Svyatoslav Ryhel
2026-02-10 13:35 ` Rob Herring (Arm)
2026-02-10 14:19 ` Rob Herring [this message]
2026-02-10 14:28 ` Svyatoslav Ryhel
2026-02-11 6:27 ` Claude review: " Claude Code Review Bot
2026-02-10 9:49 ` [PATCH v1 2/2] ARM: tegra: transformers: add connector node Svyatoslav Ryhel
2026-02-11 6:27 ` Claude review: " Claude Code Review Bot
2026-02-11 6:27 ` Claude review: ARM: tegra: document Tegra20 HDMI port Claude Code Review Bot
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=20260210141917.GA2659856-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.com \
--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