dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Michael Klein <michael@fossekall.de>
To: Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>
Cc: dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] [BISECTED] drm/sun4i: hdmi: No HDMI output with BananaPI M1 on 6.9
Date: Mon, 26 May 2025 18:56:35 +0200	[thread overview]
Message-ID: <aDSdQwwMYQHYX5Rn@a98shuttle.de> (raw)
In-Reply-To: <aCJZmm8rC0RwbcBX@a98shuttle.de>

On Mon, May 12, 2025 at 10:27:07PM +0200, Michael wrote:
>with v6.9 and later there is no output on the BananaPI HDMI connector.
>
>I have bisected the issue to the following commit:
>
>  358e76fd613a ("drm/sun4i: hdmi: Consolidate atomic_check and mode_valid")
>
>With this patch, sun4i_hdmi_connector_clock_valid() is occasionally 
>called with clock=0, causing the function to return MODE_NOCLOCK.
>In the old sun4i_hdmi_mode_valid() before the patch, mode->clock is 
>always!=0, maybe that gives someone a hint.

#regzbot introduced: 358e76fd613a

  reply	other threads:[~2025-05-26 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 20:27 [REGRESSION] [BISECTED] drm/sun4i: hdmi: No HDMI output with BananaPI M1 on 6.9 Michael
2025-05-26 16:56 ` Michael Klein [this message]
2025-05-26 17:30 ` Maxime Ripard
2025-05-26 21:13   ` Michael
2025-06-02  9:55     ` Maxime Ripard
2025-06-02 18:40       ` Michael Klein
2025-06-02 20:22         ` Michael Klein

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=aDSdQwwMYQHYX5Rn@a98shuttle.de \
    --to=michael@fossekall.de \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=samuel@sholland.org \
    --cc=tzimmermann@suse.de \
    --cc=wens@csie.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).