public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aradhya Bhatia <aradhya.bhatia@linux.dev>
To: Vicente Bergas <vicencb@gmail.com>
Cc: Laurent.pinchart@ideasonboard.com, airlied@gmail.com,
	alexander.sverdlin@siemens.com, andrzej.hajda@intel.com,
	devarsht@ti.com, dri-devel <dri-devel@lists.freedesktop.org>,
	jernej.skrabec@gmail.com, Jonas Karlman <jonas@kwiboo.se>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	lumag@kernel.org, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, neil.armstrong@linaro.org, nm@ti.com,
	rfoss@kernel.org, simona@ffwll.ch,
	tomi.valkeinen@ideasonboard.com, tzimmermann@suse.de,
	vigneshr@ti.com
Subject: Re: [PATCH v13 3/4] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable
Date: Thu, 11 Sep 2025 09:01:50 +0100	[thread overview]
Message-ID: <bea50d14-2311-46ad-bb30-9d60a4c5e3a2@linux.dev> (raw)
In-Reply-To: <CAAMcf8BfxMJx+5ttEXx0kONP2OYWSLFqEYF6rfVBKoRg5TKZzQ@mail.gmail.com>

Hi Vicente,

Thank you for the bisection and reporting the issue.

On 10/09/25 16:17, Vicente Bergas wrote:
> Hi,
> this patch causes a regression. It has been reported in
> https://bugzilla.kernel.org/show_bug.cgi?id=220554
> 
> It affects the gru/kevin platform (arm64,RK3399) with the Panfrost DRM driver.

I believe the Panfrost DRM driver may only be for the GPU.

Based on the dts files in arm64/rockchip/, this is the pipeline of the
gru-kevin setup that I understand.

	rk3399-vop (Big/Lite) -> rk3399-edp -> sharp,lq123p (edp-panel)

The setup seems to be using the drm/rockchip drivers for the display
controller and for the bridge.

> 
> When it boots in console mode, the blinking of the cursor keeps the display on.
> If it is turned off via /sys/class/graphics/fbcon/cursor_blink, then
> the display briefly shows each key press presented on screen for less
> than one second and then powers off.
> 
> When starting the graphical mode (wayland), if there are no
> applications drawing on the screen, the only way to keep the display
> on is by continuously moving the mouse.
> 

Okay!

I will have a look through the drivers. In the meanwhile, please do
report back if you find any other observations.


-- 
Regards
Aradhya


  reply	other threads:[~2025-09-11  8:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 15:17 [PATCH v13 3/4] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable Vicente Bergas
2025-09-11  8:01 ` Aradhya Bhatia [this message]
2025-10-06 15:30   ` Aradhya Bhatia
2025-12-01 19:34     ` Vicente Bergas
2025-12-02  6:29       ` Laurent Pinchart
2025-12-03  3:43     ` Chaoyi Chen
  -- strict thread matches above, loose matches on Subject: below --
2025-06-05 17:15 [PATCH v13 0/4] drm/atomic-helper: Re-order CRTC and Bridge ops Aradhya Bhatia
2025-06-05 17:15 ` [PATCH v13 3/4] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable Aradhya Bhatia
2025-06-11 10:45   ` Marek Szyprowski
2025-06-12  5:49     ` Tomi Valkeinen
2025-06-12  6:31       ` Marek Szyprowski
2025-06-16 15:40         ` Tomi Valkeinen
2025-06-18  6:30           ` Marek Szyprowski
2025-06-18  8:27             ` Maxime Ripard
2025-06-18 10:01               ` Marek Szyprowski
2025-06-18 10:05                 ` Tomi Valkeinen
2025-06-18 16:27                 ` Tomi Valkeinen
2025-10-22  8:24   ` Linus Walleij

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=bea50d14-2311-46ad-bb30-9d60a4c5e3a2@linux.dev \
    --to=aradhya.bhatia@linux.dev \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=alexander.sverdlin@siemens.com \
    --cc=andrzej.hajda@intel.com \
    --cc=devarsht@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=nm@ti.com \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    --cc=vicencb@gmail.com \
    --cc=vigneshr@ti.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