On 21/03/2023 22:35, Konrad Dybcio wrote:
> The DSI compatible changed between patchset revisions, but that wasn't
> reflected in the bindings. Fix it.
>
> Fixes: 430e11f42bff ("dt-bindings: display: msm: Add qcom, sm8350-mdss
> binding")
> Signed-off-by: Konrad Dybcio
> ---
Acked-by: Krzyszto
On Tue, Mar 21, 2023 at 04:54:51PM +0200, Dmitry Baryshkov wrote:
> On 06/03/2023 12:07, Johan Hovold wrote:
> > Make sure to free the DRM device also in case of early errors during
> > bind().
> >
> > Fixes: 2027e5b3413d ("drm/msm: Initialize MDSS irq domain at probe time")
> > Cc: sta...@vger.ke
On Tue, Mar 21, 2023 at 05:21:56PM +0200, Dmitry Baryshkov wrote:
> On 21/03/2023 15:02, Johan Hovold wrote:
> > On Mon, Mar 06, 2023 at 11:07:12AM +0100, Johan Hovold wrote:
> >> I had reasons to look closer at the MSM DRM driver error handling and
> >> realised that it had suffered from a fair am
V2 adds missing AR30 swizzles in dpu_format_map_ubwc to avoid the following
errors:
[drm:dpu_get_dpu_format_ext:1044] [dpu error]unsupported fmt: AR30 modifier
0x501
msm_dpu ae01000.display-controller: [drm:msm_framebuffer_init] *ERROR*
unsupported pixel format: AR30
On Tue, Mar 21, 2023 at 8:08 AM Randy Dunlap wrote:
>
>
>
> On 3/6/23 01:06, Geert Uytterhoeven wrote:
> > With gcc-5 and CONFIG_UBSAN_SHIFT=y:
> >
> > drivers/gpu/drm/msm/msm_mdss.c: In function 'msm_mdss_enable':
> > drivers/gpu/drm/msm/msm_mdss.c:296:2: error: case label does not reduce
