From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 566A412AAF5; Sun, 24 Mar 2024 22:55:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711320942; cv=none; b=IUBN45jF9wD8VZmlRIKSWhM7pTEMiK2sphxj8g/SQ7AJzjMSlvy4nqMgVTPznksOmv6Le9DjrCgGQPJWrr0qy7bSUGGRLn6wwBF/ayPDSgGDQnaf5+A/RpUh5NarvI+eHHk/I1BLHkUGvso3uXdCmHncJCYOqb1dmc9RJlnb7vY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711320942; c=relaxed/simple; bh=3Wzt/MY03JIIh8DBekuR6xPd27GDZod/Rv/dJ5fef9Q=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=HZuSVw5sdEbyPpwRPpK87ZLdwTufy1yIiyadQv1KcmclUHsPftMSxzbvg3RY5fOYkgdlwW+97zl48IE28ed5fYZGDtNWVKTJnKOKpGOU759uMrg6Enp5vEe3/dwhnp53iat5LuoR7nPyhlaLjEFqw8YXac8PuMIESevrqjYcULU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=S85FT92m; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="S85FT92m" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 927C1C433A6; Sun, 24 Mar 2024 22:55:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711320942; bh=3Wzt/MY03JIIh8DBekuR6xPd27GDZod/Rv/dJ5fef9Q=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=S85FT92m3DUl6KLzZ6oVrvsrcLAGzVSsWshbfzslbjxd2w2Fk4cFtRh/3mQaoB69h n+FJREHSpndVgJVN5/+rcK80ZvzRzbB7XIR8M7jBapIFRVtkE14ED4KEPzunQFTlKF My6U8we0TIDm99kOiWaLR/KW+eDdgC6JRuPDTMbdZmsiOZNeuGDycT+0eSAvd7YUG7 o5viK44oGTlLN00IZt/+F3HKr/4jsm9Ph5bJ+eaDMtD9vNj+nM04T2qARVr8JCpImz qPWFkNnuwrD3QmoXEOL7uX4CdhXXSc+0xrvITpZvNuvBGNMU6T17+vT1294ZdjXZei kuQh8ixfcwbVw== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Tomi Valkeinen , Aradhya Bhatia , Sasha Levin Subject: [PATCH 6.7 505/713] drm/tidss: Fix initial plane zpos values Date: Sun, 24 Mar 2024 18:43:51 -0400 Message-ID: <20240324224720.1345309-506-sashal@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240324224720.1345309-1-sashal@kernel.org> References: <20240324224720.1345309-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit From: Tomi Valkeinen [ Upstream commit 3ec948ccb2c4b99e8fbfdd950adbe92ea577b395 ] When the driver sets up the zpos property it sets the default zpos value to the HW id of the plane. That is fine as such, but as on many DSS versions the driver arranges the DRM planes in a different order than the HW planes (to keep the non-scalable planes first), this leads to odd initial zpos values. An example is J721e, where the initial zpos values for DRM planes are 1, 3, 0, 2. In theory the userspace should configure the zpos values properly when using multiple planes, and in that sense the initial zpos values shouldn't matter, but there's really no reason not to fix this and help the userspace apps which don't handle zpos perfectly. In particular, some versions of Weston seem to have issues dealing with the planes with the current default zpos values. So let's change the zpos values for the DRM planes to 0, 1, 2, 3. Another option would be to configure the planes marked as primary planes to zpos 0. On a two display system this would give us plane zpos values of 0, 0, 1, 2. The end result and behavior would be very similar in this option, and I'm not aware that this would actually help us in any way. So, to keep the code simple, I opted for the 0, 1, 2, 3 values. Fixes: 32a1795f57ee ("drm/tidss: New driver for TI Keystone platform Display SubSystem") Reviewed-by: Aradhya Bhatia Signed-off-by: Tomi Valkeinen Link: https://patchwork.freedesktop.org/patch/msgid/20240213-tidss-fixes-v1-1-d709e8dfa505@ideasonboard.com Signed-off-by: Sasha Levin --- drivers/gpu/drm/tidss/tidss_plane.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/tidss/tidss_plane.c b/drivers/gpu/drm/tidss/tidss_plane.c index e1c0ef0c3894c..68fed531f6a7f 100644 --- a/drivers/gpu/drm/tidss/tidss_plane.c +++ b/drivers/gpu/drm/tidss/tidss_plane.c @@ -213,7 +213,7 @@ struct tidss_plane *tidss_plane_create(struct tidss_device *tidss, drm_plane_helper_add(&tplane->plane, &tidss_plane_helper_funcs); - drm_plane_create_zpos_property(&tplane->plane, hw_plane_id, 0, + drm_plane_create_zpos_property(&tplane->plane, tidss->num_planes, 0, num_planes - 1); ret = drm_plane_create_color_properties(&tplane->plane, -- 2.43.0