From: "Noralf Trønnes" <noralf@tronnes.org>
To: andriy.shevchenko@linux.intel.com
Cc: andy@kernel.org, deller@gmx.de, dri-devel@lists.freedesktop.org,
gregkh@linuxfoundation.org, hkallweit1@gmail.com,
lee.jones@linaro.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
michael.hennerich@analog.com, phil@philpotter.co.uk,
zhangxuezhi1@yulong.com
Subject: Re: [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance
Date: Wed, 26 Jan 2022 14:15:29 +0100 [thread overview]
Message-ID: <dc392272-80ae-dbbd-df26-c7ffa6239cf0@tronnes.org> (raw)
In-Reply-To: <20220125202118.63362-1-andriy.shevchenko@linux.intel.com>
>
> Since we got a maintainer for fbdev, I would like to
> unorphan fbtft (with the idea of sending PRs to Helge)
> and move it out of staging since there is no more clean
> up work expected and no more drivers either.
>
> Thoughts?
Here's a driver I have been working on:
drm/panel: Add MIPI DBI compatible SPI driver
https://lore.kernel.org/dri-devel/20220125175700.37408-1-noralf@tronnes.org/
It should replace the SPI part of these fbtft drivers if accepted:
$ grep -lr MIPI_DCS drivers/staging/fbtft/ | grep -v "-" | uniq | sort
drivers/staging/fbtft/fb_hx8340bn.c
drivers/staging/fbtft/fb_hx8353d.c
drivers/staging/fbtft/fb_hx8357d.c
drivers/staging/fbtft/fb_ili9163.c
drivers/staging/fbtft/fb_ili9340.c
drivers/staging/fbtft/fb_ili9341.c
drivers/staging/fbtft/fb_ili9481.c
drivers/staging/fbtft/fb_ili9486.c
drivers/staging/fbtft/fb_s6d02a1.c
drivers/staging/fbtft/fb_st7735r.c
drivers/staging/fbtft/fb_st7789v.c
drivers/staging/fbtft/fb_tinylcd.c
There's no support for the parallel interface on these controllers in
drm. Support could be added to drivers/gpu/drm/drm_mipi_dbi.c.
Here's a status report I wrote 2 years ago:
fbtft: 5 years in staging
https://lore.kernel.org/dri-devel/a6cef26c-0f4b-47f0-d249-71f53891526b@tronnes.org/
Noralf.
next prev parent reply other threads:[~2022-01-26 13:15 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 20:21 [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 1/4] fbtft: Unorphan the driver Andy Shevchenko
2022-01-26 8:31 ` Greg Kroah-Hartman
2022-01-26 10:31 ` Daniel Vetter
2022-01-26 11:17 ` Helge Deller
2022-01-26 11:26 ` Greg Kroah-Hartman
2022-01-26 13:12 ` Andy Shevchenko
2022-01-26 13:46 ` Javier Martinez Canillas
2022-01-26 14:08 ` Andy Shevchenko
2022-01-26 14:10 ` Andy Shevchenko
2022-01-26 14:15 ` Javier Martinez Canillas
2022-01-31 8:29 ` Javier Martinez Canillas
2022-01-31 9:18 ` Thomas Zimmermann
2022-01-31 10:18 ` Javier Martinez Canillas
2022-01-31 10:28 ` Thomas Zimmermann
2022-02-01 17:00 ` Geert Uytterhoeven
2022-02-01 17:06 ` Daniel Vetter
2022-02-01 19:00 ` Thomas Zimmermann
2022-01-31 11:36 ` Andy Shevchenko
2022-01-31 12:08 ` Javier Martinez Canillas
2022-01-31 13:23 ` Andy Shevchenko
2022-01-31 13:24 ` Andy Shevchenko
2022-01-31 13:55 ` Javier Martinez Canillas
2022-01-31 14:06 ` Andy Shevchenko
2022-01-26 17:34 ` Jani Nikula
2022-01-26 11:27 ` Daniel Vetter
2022-01-26 13:14 ` Andy Shevchenko
2022-01-26 11:31 ` Thomas Zimmermann
2022-01-26 13:13 ` Andy Shevchenko
2022-01-26 13:07 ` Andy Shevchenko
2022-01-26 13:06 ` Andy Shevchenko
2022-01-26 13:22 ` Daniel Stone
2022-01-25 20:21 ` [PATCH v1 2/4] fbtft: Move driver out from staging Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 3/4] fbtft: Kill outdated documentation Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 4/4] fbtft: Replace 'depends on FB_TFT' by 'if FB_TFT ... endif' Andy Shevchenko
2022-01-25 20:40 ` Randy Dunlap
2022-01-26 8:54 ` Joe Perches
2022-01-26 13:02 ` Andy Shevchenko
2022-01-26 8:52 ` [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance Thomas Zimmermann
2022-01-26 10:02 ` Andy Shevchenko
2022-01-26 10:04 ` Andy Shevchenko
2022-01-26 10:28 ` Dan Carpenter
2022-01-26 12:37 ` Javier Martinez Canillas
2022-01-26 12:56 ` Greg Kroah-Hartman
2022-01-26 13:18 ` Andy Shevchenko
2022-01-26 13:44 ` Javier Martinez Canillas
2022-01-26 13:19 ` Javier Martinez Canillas
2022-01-26 13:36 ` Andy Shevchenko
2022-01-26 13:17 ` Andy Shevchenko
2022-01-26 10:43 ` Daniel Vetter
2022-01-26 10:47 ` Greg Kroah-Hartman
2022-01-26 10:52 ` Daniel Vetter
2022-01-26 11:15 ` Greg Kroah-Hartman
2022-01-26 13:26 ` Andy Shevchenko
2022-01-26 13:24 ` Andy Shevchenko
2022-01-26 10:59 ` Helge Deller
2022-01-26 11:18 ` Javier Martinez Canillas
2022-01-26 11:24 ` Daniel Vetter
2022-01-26 11:38 ` Helge Deller
2022-01-26 11:45 ` Sven Schnelle
2022-01-26 13:30 ` Andy Shevchenko
2022-01-27 9:18 ` Maxime Ripard
2022-01-26 11:31 ` Helge Deller
2022-01-26 11:38 ` Greg Kroah-Hartman
2022-01-26 11:51 ` Helge Deller
2022-01-26 12:15 ` Greg Kroah-Hartman
2022-01-26 11:51 ` Thomas Zimmermann
2022-01-26 13:27 ` Andy Shevchenko
2022-01-26 13:47 ` Javier Martinez Canillas
2022-01-26 14:11 ` Andy Shevchenko
2022-01-26 14:18 ` Javier Martinez Canillas
2022-01-26 14:24 ` Greg Kroah-Hartman
2022-01-26 14:45 ` Dan Carpenter
2022-01-26 22:31 ` Daniel Vetter
2022-01-27 6:29 ` Dan Carpenter
2022-01-27 10:32 ` Dmitry Vyukov
2022-01-27 11:11 ` Daniel Vetter
2022-01-27 16:34 ` Dmitry Vyukov
2022-01-26 22:37 ` Daniel Vetter
2022-01-26 11:41 ` Thomas Zimmermann
2022-01-26 13:32 ` Andy Shevchenko
2022-01-26 15:02 ` Thomas Zimmermann
2022-01-26 15:33 ` Andy Shevchenko
2022-01-26 15:54 ` Helge Deller
2022-01-26 13:15 ` Noralf Trønnes [this message]
2022-01-26 13:21 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc392272-80ae-dbbd-df26-c7ffa6239cf0@tronnes.org \
--to=noralf@tronnes.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=michael.hennerich@analog.com \
--cc=phil@philpotter.co.uk \
--cc=zhangxuezhi1@yulong.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).