From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta1.migadu.com (out-173.mta1.migadu.com [95.215.58.173]) (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 14CB9334C18 for ; Tue, 27 Jan 2026 09:43:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769507032; cv=none; b=PFtxr/Ydz77wPqxgYVcriMKUI5cr6EAEgIMTfjtLVckajvmmo1iLwVRyYG2DH08tD+BW/IT7nlVsDEZHDeAaFW5qBYpn7SbGo9GSr1uP1UzCA8ykZe8MZT6fdRhpRKrzq4qmTZdcSj9OfZH7wRj1iy9C99ICD6NZeJe6Mx9CSPE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769507032; c=relaxed/simple; bh=G01lHAfwUNP/fW/Xl9YZTCoD8RDMZu5h9EXF8RjXpMU=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=swdiLhebbcRBaSzPBNUorEK77aXsJoV3yfow2sXYcKSPfnqiydqe3RzxSnOppriHMnxbpJqAJiZgiePINA/hBYX6sJs5Ws017qZ4HFMAPqStdVU2cNlkR1+LwKDQIM/yrnp6IunMYcZR38TfMwY0St9PGnMUiBEzsxKOiu2L2Uc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=packett.cool; spf=pass smtp.mailfrom=packett.cool; dkim=pass (2048-bit key) header.d=packett.cool header.i=@packett.cool header.b=i6hy5OhT; arc=none smtp.client-ip=95.215.58.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=packett.cool Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=packett.cool Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=packett.cool header.i=@packett.cool header.b="i6hy5OhT" Message-ID: <33424a9d-10a6-4479-bba6-12f8ce60da1a@packett.cool> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packett.cool; s=key1; t=1769507026; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bdTrt5yTViLMoxGqfPI2tzzVWJf6+qHces4GsCpsQDw=; b=i6hy5OhTkrEK1JWbJlqEJ6KvqNDCm4DL9hLJul51zp0E4tHfqYHY4QfWaTutTtwgajhw+A k4CFnhPvrInf+TwZPm2/+/6Msf48vLqeJZbTqt1wM7hEJlbQczpQc+krZK+FbG96NuR/55 q0tOiHQzlscw/JxmGwq6n1ThmwY/X1LHXI1g1s7XVXKJcl5goG9f10/5wE1LsJDc0g3a/z Dx016l4YYXoOoVWJGpH0304hs9WEVndY/6PK4Wb1RBc1cfyKd8akP3KhMEeWDFRhUeCJRK oiEgfnO9cvUeY2uMJ0xKU/JpPQ8slVJ4NES3f4m25kXNOWM7VcdN2fb22NRgfg== Date: Tue, 27 Jan 2026 06:43:32 -0300 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH 2/2] drm/msm/dpu: try reserving the DSPP-less LM first To: Dmitry Baryshkov , Rob Clark , Abhinav Kumar , Jessica Zhang , Sean Paul , Marijn Suijten , David Airlie Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org References: <20260115-dpu-fix-dspp-v1-0-b73152c147b3@oss.qualcomm.com> <20260115-dpu-fix-dspp-v1-2-b73152c147b3@oss.qualcomm.com> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Val Packett In-Reply-To: <20260115-dpu-fix-dspp-v1-2-b73152c147b3@oss.qualcomm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT Hi, On 1/15/26 5:05 PM, Dmitry Baryshkov wrote: > On most of the platforms only some mixers have connected DSPP blocks. > If DSPP is not required for the CRTC, try looking for the LM with no > DSSP block, leaving DSPP-enabled LMs to CRTCs which actually require > those. > > Signed-off-by: Dmitry Baryshkov > --- > drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 52 +++++++++++++++++++++++++--------- > 1 file changed, 38 insertions(+), 14 deletions(-) this has massively broken things on my x1e device (latitude-7455): - upon booting into gdm, the internal display is all dark blue - suspend-resume makes gdm appear fine, then logging in results in another blue screen, again bypassed by suspend-resume (vt switching back to gdm makes it appear fine but switching back to the session, it's still blue) - OR blindly logging in on the blue gdm makes the session appear - plugging in an external display makes the blue screen flash constantly over the contents, there is also a flashing vertical gap between 2 halves of the internal screen (amazing effect) and the external display doesn't actually refresh the contents under the blue (https://owo.packett.cool/dbg/dspp-lm-boom.webm) Consistently across 3 reboots. Reverted only this commit and it's back to normal, so I'm pretty sure it's this. /sys/kernel/debug/dri..: https://owo.packett.cool/dbg/bluewtf.dri ~val