[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YfFE61IQus3SMQRZ@kroah.com>
Date: Wed, 26 Jan 2022 13:56:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Javier Martinez Canillas <javierm@...hat.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Andy Shevchenko <andy@...nel.org>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@...r.kernel.org>,
Michael Hennerich <michael.hennerich@...log.com>,
Helge Deller <deller@....de>, linux-staging@...ts.linux.dev,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Phillip Potter <phil@...lpotter.co.uk>,
Thomas Zimmermann <tzimmermann@...e.de>,
Carlis <zhangxuezhi1@...ong.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance
On Wed, Jan 26, 2022 at 01:37:00PM +0100, Javier Martinez Canillas wrote:
> On 1/26/22 11:28, Dan Carpenter wrote:
> > On Wed, Jan 26, 2022 at 12:04:26PM +0200, Andy Shevchenko wrote:
> >> On Wed, Jan 26, 2022 at 12:02 PM Andy Shevchenko
> >> <andy.shevchenko@...il.com> wrote:
> >>> On Wed, Jan 26, 2022 at 10:52 AM Thomas Zimmermann <tzimmermann@...e.de> wrote:
> >>>> Am 25.01.22 um 21:21 schrieb Andy Shevchenko:
> >>
> >> ...
> >>
> >>>> But why? We already have DRM drivers for some of these devices.
> >>>
> >>> No, we do not (only a few are available).
> >>
> >> Sorry, I missed your word 'some'. Some == almost none from the list (I
> >> don't remember exact numbers but something like 2 out of 10 are
> >> supported by tiny DRM and see about interfaces).
> >
> > Could we get an exact list?
> >
>
> The list AFAICT is the following. I'm not familiar with these so please
> feel free to correct anything I got wrong here.
>
> I've marked with '?' if found references to the device supported by the
> fbdev driver in a DRM driver, but it's not clear if support the same HW.
>
> Drivers in drivers/staging/fbtft:
>
> fb_agm1264k-fl.c
> fb_bd663474.c
> fb_hx8340bn.c
> fb_hx8347d.c (DRM driver in drivers/gpu/drm/tiny/hx8357d.c)
> fb_hx8353d.c
> fb_hx8357d.c (DRM driver in drivers/gpu/drm/tiny/hx8357d.c)
> fb_ili9163.c (DRM driver in drivers/gpu/drm/tiny/ili9163.c)
> fb_ili9320.c
> fb_ili9325.c
> fb_ili9340.c (DRM driver in drivers/gpu/drm/tiny/mi0283qt.c ?)
> fb_ili9341.c (DRM driver in drivers/gpu/drm/tiny/mi0283qt.c ?)
> fb_ili9481.c
> fb_ili9486.c (DRM driver in drivers/gpu/drm/tiny/ili9486.c)
> fb_pcd8544.c
> fb_ra8875.c
> fb_s6d02a1.c
> fb_s6d1121.c
> fb_seps525.c
> fb_sh1106.c
> fb_ssd1289.c
> fb_ssd1305.c
> fb_ssd1306.c
> fb_ssd1325.c
> fb_ssd1331.c
> fb_ssd1351.c
> fb_st7735r.c (DRM driver in drivers/gpu/drm/tiny/st7735r.c)
> fb_st7789v.c (DRM driver in drivers/gpu/drm/panel/panel-sitronix-st7789v.c)
I'll gladly take a patch that deletes the fb_* files that are already
handled by a DRM driver like you list here.
thanks,
greg k-h
Powered by blists - more mailing lists