bugs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	andy@chernyak.nl,
	DRI Development	 <dri-devel@lists.freedesktop.org>,
	"moderated list:ARM/Mediatek SoC support"	
	<linux-mediatek@lists.infradead.org>
Cc: bugs@lists.linux.dev, granquet@baylibre.com,
	 angelogioacchino.delregno@collabora.com
Subject: Re: Commit d6e25b3590 breaks external video (HDMI) on mt8173 (chromebook oak)
Date: Mon, 18 Aug 2025 16:42:54 +0200	[thread overview]
Message-ID: <dfb0e47c755f2e055887c421b25dbcf575eb2dbb.camel@collabora.com> (raw)
In-Reply-To: <CAAOTY_8L_tJwL77wqBVxrmoMLEGgXue8wW5dz8TLfUg4Ehn4dw@mail.gmail.com>

Hi Andy,

On Thu, 2025-08-14 at 22:38 +0800, Chun-Kuang Hu wrote:
> Forward to dri-devel and linux-mediatek.
> 
> Andy Chernyak <andy.chernyak@gmail.com> 於 2025年7月2日 週三 下午11:12寫道:
> > 
> > Kernel 6.16 has external video (both hdmi and displayport-over-
> > usbc) broken (black screen) on mt8173-based chromebooks (platform
> > codename "oak", device codename "hana"). Bisect points finger to
> > following commit:
> > 
> > From d6e25b3590a0679bca1a1becc04e3999f1dfd461
> > From: Guillaume Ranquet <granquet@baylibre.com>
> > Date: Tue, 15 Apr 2025 12:43:05 +0200
> > Subject: drm/mediatek: hdmi: Use regmap instead of iomem for main
> > registers
> > In preparation for the addition of a new version of the HDMI IP
> > which will need to share its iospace between multiple subdrivers,
> > and in preparation for moving out the common bits between the two,
> > migrate this driver to fully use regmap.
> > 
> > Reverting d6e25b3590 with "patch -R" on top of 6.16-rc4 fixes this.

thank you for the bug report.

By reading and checking this patch changes, I found two modifications
that looked incorrect, so I sent a patch to fix them:
https://lore.kernel.org/dri-devel/20250818-mt8173-fix-hdmi-issue-v1-1-55aff9b0295d@collabora.com/

Since I don't have any mt8173-based board myself, could you test this
patch and tell if it does fix the issue (or not)?

Looking forward to your reply,

Regards,
Louis-Alexis

      reply	other threads:[~2025-08-18 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHjEvi5mb+1-zD+x1_Bp_0Z2Aov7KDyFksbU4PZKFxmrPa77VQ@mail.gmail.com>
2025-08-14 14:38 ` Commit d6e25b3590 breaks external video (HDMI) on mt8173 (chromebook oak) Chun-Kuang Hu
2025-08-18 14:42   ` Louis-Alexis Eyraud [this message]

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=dfb0e47c755f2e055887c421b25dbcf575eb2dbb.camel@collabora.com \
    --to=louisalexis.eyraud@collabora.com \
    --cc=andy@chernyak.nl \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bugs@lists.linux.dev \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=granquet@baylibre.com \
    --cc=linux-mediatek@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).