From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] fbdev: sh_mobile_meram: use ARCH_RENESAS
Date: Wed, 16 Mar 2016 05:26:58 +0000 [thread overview]
Message-ID: <1746404.X3VTt1eR6F@avalon> (raw)
In-Reply-To: <1457663298-31973-2-git-send-email-horms+renesas@verge.net.au>
Hi Simon,
On Tuesday 15 March 2016 10:25:30 Simon Horman wrote:
> On Fri, Mar 11, 2016 at 09:22:08AM +0200, Laurent Pinchart wrote:
> > On Friday 11 March 2016 09:14:46 Laurent Pinchart wrote:
> > > On Friday 11 March 2016 11:28:17 Simon Horman wrote:
> > > > Use ARCH_RENESAS in place of ARCH_SHMOBILE.
> > > > Also remove spurious ().
> > > >
> > > > This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> > > > ARCH_RENESAS the motivation for which being that RENESAS seems to be a
> > > > more appropriate name than SHMOBILE for the majority of Renesas ARM
> > > > based SoCs.
> > > >
> > > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > > > ---
> > > >
> > > > drivers/video/fbdev/Kconfig | 4 ++--
> > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
> > > > index 8ea45a5cd806..71294f595f61 100644
> > > > --- a/drivers/video/fbdev/Kconfig
> > > > +++ b/drivers/video/fbdev/Kconfig
> > > > @@ -1985,7 +1985,7 @@ config FB_W100
> > > >
> > > > config FB_SH_MOBILE_LCDC
> > > >
> > > > tristate "SuperH Mobile LCDC framebuffer support"
> > > >
> > > > - depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
> > > > + depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
> > > >
> > > > depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
> > > > select FB_SYS_FILLRECT
> > > > select FB_SYS_COPYAREA
> > > >
> > > > @@ -2450,7 +2450,7 @@ source "drivers/video/fbdev/mmp/Kconfig"
> > > >
> > > > config FB_SH_MOBILE_MERAM
> > > >
> > > > tristate "SuperH Mobile MERAM read ahead support"
> > > >
> > > > - depends on (SUPERH || ARCH_SHMOBILE)
> > > > + depends on SUPERH || ARCH_RENESAS
> > >
> > > The MERAM driver isn't used by any ARM platform, you can just drop
> > > ARCH_SHMOBILE completely.
> >
> > Actually, upon closer inspection, the MERAM driver isn't used by any
> > platform.
>
> If its not used then I think we should consider removing it.
>
> However, it seems to me that its used in the following:
>
> drivers/gpu/drm/shmobile/shmob_drm_crtc.c
> drivers/gpu/drm/shmobile/shmob_drm_kms.c
> drivers/gpu/drm/shmobile/shmob_drm_plane.c
> drivers/video/fbdev/sh_mobile_lcdcfb.c
>
> It seems to me that we would need to either remove usage in the above
> files or remove the above files before removing the MERAM driver.
That's correct, those drivers need to be fixed or removed.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-03-16 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 2:28 [PATCH 1/2] fbdev: sh_mobile_meram: use ARCH_RENESAS Simon Horman
2016-03-11 7:14 ` Laurent Pinchart
2016-03-11 7:22 ` Laurent Pinchart
2016-03-11 7:55 ` Geert Uytterhoeven
2016-03-14 0:13 ` Simon Horman
2016-03-15 1:25 ` Simon Horman
2016-03-16 5:26 ` Laurent Pinchart [this message]
2016-03-16 6:31 ` Magnus Damm
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=1746404.X3VTt1eR6F@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).