From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Luis de Arquer <ldearquer@gmail.com>,
Alexandre ARNOUD <aarnoud@me.com>
Cc: kernel@collabora.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
FUKAUMI Naoki <naoki@radxa.com>
Subject: Re: [PATCH v2 0/5] Enable HDMI0 on several RK3588 based boards
Date: Tue, 22 Oct 2024 18:29:32 +0200 [thread overview]
Message-ID: <2a27ed62-305d-4d41-a43f-02f58bc22e2d@linaro.org> (raw)
In-Reply-To: <20241019-rk3588-hdmi0-dt-v2-0-466cd80e8ff9@collabora.com>
W dniu 19.10.2024 o 12:12, Cristian Ciocaltea pisze:
> Since the initial support for the RK3588 HDMI TX Controller [1] has been
> merged as of next-20241018, let's enable the HDMI0 output port for the
> following boards: Radxa ROCK 5A & 5B, Rockchip RK3588 EVB1 V10, Xunlong
> Orange Pi 5+.
I copied changes to FriendlyELEC NanoPC-T6 DT and booted 6.12-rc3 with
your changes on LTS variant of the board.
With my SBC monitor it complained about resolution (10.5" 1366x768px):
rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster0-win0
actual_w[1366] not 4 pixel aligned
And monitor told me "no signal".
/sys/devices/platform/display-subsystem/drm/card1/card1-HDMI-A-1/modes
lists all resolutions available.
Would be nice to see system going to next EDID resolution in such case.
1280x720px is 4px aligned.
With my 34" 3440x1440px monitor it shown some output once. In resolution
close to original one but 16:9 instead of 21:9 one. Anyway monitor
behaved in "I do not like that signal" way - started blinking, had
problems with displaying even from my desktop after.
I got a feeling that 1920x1080px monitor landed on my "need to buy" list.
next prev parent reply other threads:[~2024-10-22 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 10:12 Cristian Ciocaltea
2024-10-19 10:12 ` [PATCH v2 1/5] arm64: dts: rockchip: Add HDMI0 node to rk3588 Cristian Ciocaltea
2024-10-19 10:12 ` [PATCH v2 2/5] arm64: dts: rockchip: Enable HDMI0 on rock-5b Cristian Ciocaltea
2024-11-06 20:42 ` Link Mauve
2024-11-06 21:26 ` Cristian Ciocaltea
2024-10-19 10:12 ` [PATCH v2 3/5] arm64: dts: rockchip: Enable HDMI0 on rk3588-evb1 Cristian Ciocaltea
2024-10-19 10:12 ` [PATCH v2 4/5] arm64: dts: rockchip: Enable HDMI0 on orangepi-5-plus Cristian Ciocaltea
2024-10-19 10:12 ` [PATCH v2 5/5] arm64: dts: rockchip: Enable HDMI0 on rock-5a Cristian Ciocaltea
2024-10-19 13:02 ` Jonas Karlman
2024-10-19 17:44 ` Cristian Ciocaltea
2024-10-21 15:44 ` (subset) [PATCH v2 0/5] Enable HDMI0 on several RK3588 based boards Heiko Stuebner
2024-10-21 17:12 ` Diederik de Haas
2024-10-22 16:29 ` Marcin Juszkiewicz [this message]
2024-10-22 16:55 ` Cristian Ciocaltea
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=2a27ed62-305d-4d41-a43f-02f58bc22e2d@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=aarnoud@me.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=ldearquer@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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
all inboxes | Powered by JetHome®