linux-kernel - Re: [PATCH 04/21] drm/msm/dsi: support DSC configurations with slice_per

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: <CABymUCNCZFx3kMtxXt-U2L+_ks5oCCWMF0k-NyFkp99-aTqf-A@mail.gmail.com>
Date: Tue, 3 Sep 2024 15:36:26 +0800
From: Jun Nie <jun.nie@...aro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@...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>, Daniel Vetter <daniel@...ll.ch>, 
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>, 
	Thomas Zimmermann <tzimmermann@...e.de>, linux-arm-msm@...r.kernel.org, 
	dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org, 
	linux-kernel@...r.kernel.org, Jonathan Marek <jonathan@...ek.ca>
Subject: Re: [PATCH 04/21] drm/msm/dsi: support DSC configurations with
 slice_per_pkt > 1

Dmitry Baryshkov <dmitry.baryshkov@...aro.org> 于2024年8月29日周四 19:04写道：
>
> On Thu, 29 Aug 2024 at 13:19, Jun Nie <jun.nie@...aro.org> wrote:
> >
> > From: Jonathan Marek <jonathan@...ek.ca>
> >
> > MSM display controller support multiple slice to be sent in a single DSC
> > packet.
>
> This is not MSM-specific. It is allowed per the standard.

I do not find it in VESA standard 1.1 and 1.2a. Could you help point
me the standard
link?
>
> > Add a dsc_slice_per_pkt field to mipi_dsi_device struct and
> > support this field in msm mdss driver.
>
> This doesn't describe why this is necessary at all. Is it a fix or a feature?

It is a feature per the name. But I do not know more than the code from QCOM.
And different value other than 1 is needed for some panel with QCOM
SoC per test.
 So I suppose it is a key parameter. Any more idea?

>