public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Franz Schnyder <fra.schnyder@gmail.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Franz Schnyder <franz.schnyder@toradex.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] arm64: dts: ti: k3-am69-aquila: Fix DP enable GPIO
Date: Mon, 2 Feb 2026 10:12:54 +0100	[thread overview]
Message-ID: <20260202091254.GA33026@francesco-nb> (raw)
In-Reply-To: <20260202083604.325060-1-fra.schnyder@gmail.com>

On Mon, Feb 02, 2026 at 09:35:59AM +0100, Franz Schnyder wrote:
> From: Franz Schnyder <franz.schnyder@toradex.com>
> 
> Correct the DP regulator enable GPIO to index 21 on Clover and Dev board.
> The 3.3V DP regulator was not being enabled by the assigned GPIO, as it
> is routed to GPIO index 21 and not 37, which was causing instability
> with displays connected over DP or via an active DP-to-HDMI adapter.

Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>




  parent reply	other threads:[~2026-02-02  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02  8:35 [PATCH v1 0/2] arm64: dts: ti: k3-am69-aquila: Fix DP enable GPIO Franz Schnyder
2026-02-02  8:36 ` [PATCH v1 1/2] arm64: dts: ti: k3-am69-aquila-dev: Fix DP regulator " Franz Schnyder
2026-02-02  8:36 ` [PATCH v1 2/2] arm64: dts: ti: k3-am69-aquila-clover: " Franz Schnyder
2026-02-02  9:12 ` Francesco Dolcini [this message]
2026-03-13  7:46 ` [PATCH v1 0/2] arm64: dts: ti: k3-am69-aquila: Fix DP " Vignesh Raghavendra

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=20260202091254.GA33026@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fra.schnyder@gmail.com \
    --cc=franz.schnyder@toradex.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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