From: Thierry Reding <thierry.reding@gmail.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
Dmitry Osipenko <digetx@gmail.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] ARM: tegra: transformers: add connector node
Date: Thu, 27 Jul 2023 18:50:35 +0200 [thread overview]
Message-ID: <ZMKgW6eYpJVqeZJM@orome> (raw)
In-Reply-To: <5A2447D3-DB49-4788-AA05-182AF0F04ED2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
On Thu, Jul 27, 2023 at 07:26:28PM +0300, Svyatoslav Ryhel wrote:
>
>
> 27 липня 2023 р. 18:11:15 GMT+03:00, Thierry Reding <thierry.reding@gmail.com> написав(-ла):
> >On Sun, Jun 18, 2023 at 11:50:46AM +0300, Svyatoslav Ryhel wrote:
> >> All ASUS Transformers have micro-HDMI connector directly available.
> >> After Tegra HDMI got bridge/connector support, we should use connector
> >> framework for proper HW description.
> >>
> >> Tested-by: Andreas Westman Dorcsak <hedmoo@yahoo.com> # ASUS TF T30
> >> Tested-by: Robert Eckelmann <longnoserob@gmail.com> # ASUS TF101 T20
> >> Tested-by: Svyatoslav Ryhel <clamor95@gmail.com> # ASUS TF201 T30
> >> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> >> ---
> >> arch/arm/boot/dts/tegra20-asus-tf101.dts | 22 ++++++++++++++++---
> >> .../dts/tegra30-asus-transformer-common.dtsi | 21 ++++++++++++++++--
> >> 2 files changed, 38 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/arch/arm/boot/dts/tegra20-asus-tf101.dts b/arch/arm/boot/dts/tegra20-asus-tf101.dts
> >> index c2a9c3fb5b33..97350f566539 100644
> >> --- a/arch/arm/boot/dts/tegra20-asus-tf101.dts
> >> +++ b/arch/arm/boot/dts/tegra20-asus-tf101.dts
> >> @@ -82,9 +82,11 @@ hdmi@54280000 {
> >> pll-supply = <&hdmi_pll_reg>;
> >> hdmi-supply = <&vdd_hdmi_en>;
> >>
> >> - nvidia,ddc-i2c-bus = <&hdmi_ddc>;
> >> - nvidia,hpd-gpio = <&gpio TEGRA_GPIO(N, 7)
> >> - GPIO_ACTIVE_HIGH>;
> >> + port@0 {
> >> + hdmi_out: endpoint {
> >> + remote-endpoint = <&connector_in>;
> >> + };
> >> + };
> >
> >Does this need a bindings change? nvidia,tegra20-hdmi currently doesn't
> >support OF graphs, so this would probably fail to validate if we merge
> >it without a corresponding DT bindings update.
>
> drm/tegra patch is backwards compatible and connector node is optional.
We still need to document the connector node, otherwise the DT
validation will complain about port@0 being used here, won't it?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-27 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 8:50 [PATCH v2 0/2] Support bridge/connector by Tegra HDMI Svyatoslav Ryhel
2023-06-18 8:50 ` [PATCH v2 1/2] drm/tegra: output: hdmi: Support bridge/connector Svyatoslav Ryhel
2023-06-18 8:50 ` [PATCH v2 2/2] ARM: tegra: transformers: add connector node Svyatoslav Ryhel
2023-07-27 15:11 ` Thierry Reding
2023-07-27 16:26 ` Svyatoslav Ryhel
2023-07-27 16:50 ` Thierry Reding [this message]
2023-07-27 16:52 ` Svyatoslav Ryhel
2023-08-01 21:29 ` Maxim Schwalm
2023-07-27 15:09 ` [PATCH v2 0/2] Support bridge/connector by Tegra HDMI Thierry Reding
2023-07-27 16:24 ` Svyatoslav Ryhel
2023-07-27 16:52 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2026-02-23 6:54 [PATCH v2 0/2] ARM: tegra: document Tegra20 HDMI port Svyatoslav Ryhel
2026-02-23 6:55 ` [PATCH v2 2/2] ARM: tegra: transformers: add connector node Svyatoslav Ryhel
2026-03-27 15:18 ` Thierry Reding
2026-03-27 15:28 ` Svyatoslav Ryhel
2026-03-27 23:45 ` 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=ZMKgW6eYpJVqeZJM@orome \
--to=thierry.reding@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=maxim.schwalm@gmail.com \
--cc=mperttunen@nvidia.com \
--cc=robh+dt@kernel.org \
/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