linux-kernel - Re: [PATCH v4 01/16] drm/msm/dpu: check every pipe per capability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2mtcnk7sg7zymdbkmucby3q7uwxhb4jde5r3ym5xdwkzjw6jc5@vv6fomz45ltl>
Date: Fri, 17 Jan 2025 04:07:47 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Jun Nie <jun.nie@...aro.org>
Cc: Rob Clark <robdclark@...il.com>, 
	Abhinav Kumar <quic_abhinavk@...cinc.com>, Sean Paul <sean@...rly.run>, 
	Marijn Suijten <marijn.suijten@...ainline.org>, David Airlie <airlied@...il.com>, 
	Simona Vetter <simona@...ll.ch>, linux-arm-msm@...r.kernel.org, dri-devel@...ts.freedesktop.org, 
	freedreno@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 01/16] drm/msm/dpu: check every pipe per capability

On Thu, Jan 16, 2025 at 10:38:33PM +0800, Jun Nie wrote:
> Dmitry Baryshkov <dmitry.baryshkov@...aro.org> 于2025年1月16日周四 15:44写道：
> 
> >
> > On Thu, Jan 16, 2025 at 03:25:50PM +0800, Jun Nie wrote:
> > > Move requreiment check to routine of every pipe check. As sblk
> > > and pipe_hw_caps of r_pipe are not checked in current implementation.
> >
> How about this version?
>     The capability stored in sblk and pipe_hw_caps is checked only for
>     SSPP of the first pipe in the pair with current implementation. That
>     of the 2nd pipe, r_pipe, is not checked and may violate hardware
>     capability. Move requirement check to dpu_plane_atomic_check_pipe()
>     for the check of every pipe.

... Move SSPP feature checks to dpu_plane_atomic_check_pipe() in order
to verify requirements for every pipe.


Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>


-- 
With best wishes
Dmitry