From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: narmstrong@baylibre.com, khilman@baylibre.com,
linux-amlogic@lists.infradead.org,
dri-devel@lists.freedesktop.org, rfoss@kernel.org,
andrzej.hajda@intel.com
Cc: adrian.larumbe@collabora.com, kernel@collabora.com
Subject: [PATCH 0/3] Add additional YUV420 bus format check for dw-meson's bridge enable
Date: Sun, 28 May 2023 14:59:58 +0100 [thread overview]
Message-ID: <20230528140001.1057084-1-adrian.larumbe@collabora.com> (raw)
This is a belated follow-up on
https://lore.kernel.org/dri-devel/20220515204412.2733803-1-adrian.larumbe@collabora.com/
Commit e67f6037ae1be34b2b68 ("drm/meson: split out encoder from meson_dw_hdmi")
broke 4K display modes for me, and I discovered it was because the right pixel
clock wasn't being chosen in dw_hdmi_phy_init. I misinterpreted the reason as a
problem in figuring out whether we want to enforce YUV420 mode, but it turned
out to be a mismatch between what dw-meson code is doing and the way the bus
format is being picked by the dw-hdmi bus output format drm helper.
I fixed it by bringing back dw-hdmi bus format check in dw-meson.
The second patch makes sure YUV420 bus format is the only one being returned by
dw-hdmi's output format bridge function when that's the only drm mode allowed.
Adrián Larumbe (3):
drm/meson: dw-hdmi: change YUV420 selection logic at clock setup
dw-hdmi: truly enforce 420-only formats when drm mode demands it
dw-hdmi: remove dead code and fix indentation
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 35 +++++++++--------------
drivers/gpu/drm/meson/meson_dw_hdmi.c | 4 +--
include/drm/bridge/dw_hdmi.h | 2 ++
3 files changed, 18 insertions(+), 23 deletions(-)
--
2.40.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2023-05-28 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 13:59 Adrián Larumbe [this message]
2023-05-28 13:59 ` [PATCH 1/3] drm/meson: dw-hdmi: change YUV420 selection logic at clock setup Adrián Larumbe
2023-05-30 7:48 ` Neil Armstrong
2023-05-28 14:00 ` [PATCH 2/3] dw-hdmi: truly enforce 420-only formats when drm mode demands it Adrián Larumbe
2023-05-30 7:46 ` Neil Armstrong
2023-05-28 14:00 ` [PATCH 3/3] dw-hdmi: remove dead code and fix indentation Adrián Larumbe
2023-05-29 8:40 ` AngeloGioacchino Del Regno
2023-05-30 7:49 ` Neil Armstrong
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=20230528140001.1057084-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=rfoss@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
all inboxes | Powered by JetHome®