From: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] arm64: dts: freescale: imx95-aquila-clover: Keep DP_PWR always enabled
Date: Tue, 3 Nov 2026 14:53:44 +0200 [thread overview]
Message-ID: <aunZS4GSfuiDnrXG@vm> (raw)
In-Reply-To: <20261103105323.2394012-3-francesco@dolcini.it>
On Tue, Nov 03, 2026 at 11:53:16AM +0100, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> DP_PWR on the DisplayPort connector powers active DP cables and
> adapters, which do not work without it. Keep it always enabled, and mark
> it boot-on so that the firmware, e.g. U-Boot, enables it at boot,
> whether or not a display driver is available.
>
> Fixes: 3f519121e120 ("arm64: dts: freescale: imx95-aquila: Add Clover carrier board")
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Acked-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
--
Thanks,
Laurentiu
next prev parent reply other threads:[~2026-11-03 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:53 [PATCH v1 0/2] arm64: dts: freescale: imx95-aquila: " Francesco Dolcini
2026-11-03 10:53 ` [PATCH v1 1/2] arm64: dts: freescale: imx95-aquila-dev: " Francesco Dolcini
2026-11-03 12:53 ` Laurentiu Palcu
2026-11-03 10:53 ` [PATCH v1 2/2] arm64: dts: freescale: imx95-aquila-clover: " Francesco Dolcini
2026-11-03 12:53 ` Laurentiu Palcu [this message]
2026-11-03 12:25 ` [PATCH v1 0/2] arm64: dts: freescale: imx95-aquila: " Laurentiu Palcu
2026-11-03 12:33 ` Francesco Dolcini
2026-11-03 12:52 ` Laurentiu Palcu
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=aunZS4GSfuiDnrXG@vm \
--to=laurentiu.palcu@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.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
all inboxes | Powered by JetHome®