Re: [PATCH v2] drm/fb-helper: Scale back depth to supported maximum

2019-01-10 Thread Daniel Vetter
On Thu, Jan 10, 2019 at 10:19 AM Linus Walleij wrote: > > On Fri, Dec 28, 2018 at 5:05 PM Daniel Vetter wrote: > > On Fri, Dec 28, 2018 at 4:40 PM Linus Walleij > > wrote: > > > > - Skip over YUV formats. The framebuffer emulation cannot > > > handle these formats. > (...) > > > +

Re: [PATCH v2] drm/fb-helper: Scale back depth to supported maximum

2019-01-10 Thread Linus Walleij
On Fri, Dec 28, 2018 at 5:05 PM Daniel Vetter wrote: > On Fri, Dec 28, 2018 at 4:40 PM Linus Walleij > wrote: > > - Skip over YUV formats. The framebuffer emulation cannot > > handle these formats. (...) > > + /* Do not consider YUV formats for framebuffers */ > > +

Re: [PATCH v2] drm/fb-helper: Scale back depth to supported maximum

2018-12-28 Thread Daniel Vetter
On Fri, Dec 28, 2018 at 4:40 PM Linus Walleij wrote: > > The following happened when migrating an old fbdev driver to DRM: > > The Integrator/CP PL111 supports 16BPP but only ARGB1555/ABGR1555 > or XRGB1555/XBGR1555 i.e. the maximum depth is 15. > > This makes the initialization of the framebuffer

[PATCH v2] drm/fb-helper: Scale back depth to supported maximum

2018-12-28 Thread Linus Walleij
The following happened when migrating an old fbdev driver to DRM: The Integrator/CP PL111 supports 16BPP but only ARGB1555/ABGR1555 or XRGB1555/XBGR1555 i.e. the maximum depth is 15. This makes the initialization of the framebuffer fail since the code in drm_fb_helper_single_fb_probe() assigns th