From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B1F381C7012 for ; Tue, 2 Dec 2025 06:29:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764656982; cv=none; b=few84bgG5nGAiGLSxCGXWQrHAXxdPoOjK8TYF+s+hl+jA420wiQqBZGwQVQBAD6L+sxHhLAfvIC4MSbF+CcrjMw3L2yITCIXldQtvbeuEAV7kXzWM7W10sdwayQJlBHMaM3y/c2SfSxqAD69k1gXNKrx2frqJK1V36RMQLAEJco= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764656982; c=relaxed/simple; bh=VXzIPngFdacIDB87BOh+DyMPuMgW2UL2yvGKdB6Akqo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=uAEU4mp1yO+xibIIIqmvi0j7SNlUDfBLOPkdxrLYw0K50/gO03vsupYntmIOFFUeWeE9U+nxj0hXRaBoBHRzTO00czL/N481Z0sly27sFEoUvL0jah17Ko2C832sxTlNC9+v1JdnGtZdj82IHhE0hm83/lp2pE/BQ08QehL8i+I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=ekP/unp1; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="ekP/unp1" Received: from pendragon.ideasonboard.com (113x43x203x98.ap113.ftth.arteria-hikari.net [113.43.203.98]) by perceval.ideasonboard.com (Postfix) with UTF8SMTPSA id 8DD793E6; Tue, 2 Dec 2025 07:27:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1764656837; bh=VXzIPngFdacIDB87BOh+DyMPuMgW2UL2yvGKdB6Akqo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ekP/unp1qwNd/3Pk75lngsPPNLUJWaMpPPgy9xJEUs72B9FLPo+gGPAaGrSw5+ESs oM9gLwccqIOJdXIpmrnMph3Z9ZIQGXO5l/pfIGCtB0OGU2L6vpYeN9gMcizmM3ifOp 4V99jpxyFRBBbftE2eYRs0albkJaC6hRnU2YBifQ= Date: Tue, 2 Dec 2025 15:29:11 +0900 From: Laurent Pinchart To: Vicente Bergas Cc: Aradhya Bhatia , airlied@gmail.com, alexander.sverdlin@siemens.com, andrzej.hajda@intel.com, dri-devel , jernej.skrabec@gmail.com, Jonas Karlman , Linux Kernel Mailing List , 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, Dmitry Baryshkov , Douglas Anderson , Damon Ding , Sandy Huang , Heiko =?utf-8?Q?St=C3=BCbner?= , Andy Yan , Linux Rockchip Support List , Devarsh Thakkar , Linus Walleij , Marek Vasut Subject: Re: [PATCH v13 3/4] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable Message-ID: <20251202062911.GA24150@pendragon.ideasonboard.com> References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: +Linus, Marek and Tomi. On Mon, Dec 01, 2025 at 08:34:37PM +0100, Vicente Bergas wrote: > On Mon, Oct 6, 2025 at 5:30 PM Aradhya Bhatia wrote: > > > > +rockchip maintainers > > > > Hi Vicente, all, > > Hi everybody, > please, can some expert on this platform take a look at this bug? There are similar issues with MCDE and R-Car DU, see https://lore.kernel.org/all/CAD++jLkNCH=8VmwXh0UJS5QZ9wB-iP2kinytT+__fq0L1PzoZQ@mail.gmail.com/ I think we should revert commit c9b1150a68d9362a0827609fc0dc1664c0d8bfe1 and work on a clean solution. It broke too many drivers. > > I went through the drivers and the affected areas in the gru-kevin > > chromebook pipeline last week, but nothing has stood out. > > > > > > Pipeline: > > > > rockchip,display-subsystem / rk3399-vop (Big/Lite) (CRTC) -> > > rk3399-edp (Encoder) -> analogix_dp_core (Bridge) -> > > sharp,lq123p (edp-panel) > > > > I am unable to debug this further since I do not have the hardware. > > > > I could use some help, especially from folks who understand the hardware > > requirements better. > > > > > > On 11/09/25 09:01, Aradhya Bhatia wrote: > > > 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, Laurent Pinchart