dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	David Airlie <airlied@linux.ie>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH/RFC] drm: Remove unused Renesas SH Mobile DRM driver
Date: Tue, 22 Jan 2019 05:07:10 +0200	[thread overview]
Message-ID: <20190122030710.GA11769@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20190121101826.GT3271@phenom.ffwll.local>

Hello,

On Mon, Jan 21, 2019 at 11:18:26AM +0100, Daniel Vetter wrote:
>  On Mon, Jan 21, 2019 at 11:03:44AM +0100, Geert Uytterhoeven wrote:
> > On Mon, Jan 21, 2019 at 10:35 AM Daniel Vetter <daniel@ffwll.ch> wrote:
> >> On Fri, Jan 18, 2019 at 05:22:58PM +0100, Geert Uytterhoeven wrote:
> >>> Since its incarnation in v3.7 almost 7 years ago, no users of the SH
> >>> Mobile DRM driver have appeared.
> >>> 
> >>> Hence remove the driver.  It can be resurrected from git history,
> >>> if/when needed.
> >>> 
> >>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >> 
> >> I'd prefer removing the fbdev variant tbh ...
> > 
> > I understand ;-)
> > 
> > But sh_mobile_lcdc_fb is used on 5 legacy SuperH platforms, and 1 ARM
> > platform. At least the latter is working fine.
> > 
> >> Not sure why exactly the switch never happened.
> > 
> > Me neither.  I^HGoogle can't even find posted patches of board integration.
> > 
> > Note that both drivers lack DT support, which would be very desirable on
> > ARM, as graphics is the single remaining working driver on the Atmark
> > Techno Armadillo 800 EVA board not using DT.
>  
>  Ah I wondered why the drm driver isn't just automatically picked up in
>  today's neat world of DT (if you enable it in .config instead of the fbdev
>  one). It's not even using DT yet :-/

I'd prefer dropping the fbdev driver too, but that would require porting
the SH boards to the DRM driver, and implement DT support for the ARM
board. I don't think anyone is willing to invest time in this, so I'm
fine dropping this driver as the boards are pretty much dead. I would,
however, also drop the fbdev driver in that case.

-- 
Regards,

Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-01-22  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 16:22 [PATCH/RFC] drm: Remove unused Renesas SH Mobile DRM driver Geert Uytterhoeven
2019-01-21  9:35 ` Daniel Vetter
2019-01-21 10:03   ` Geert Uytterhoeven
2019-01-21 10:18     ` Daniel Vetter
2019-01-22  3:07       ` Laurent Pinchart [this message]
2019-01-22  8:04         ` Geert Uytterhoeven

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=20190122030710.GA11769@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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