From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 13/15] fbdev: sh-mobile-lcdcfb: Enable driver compilation with COMPILE_TEST
Date: Mon, 20 Jan 2014 15:30:21 +0000 [thread overview]
Message-ID: <5189278.VEETF0BgjA@avalon> (raw)
In-Reply-To: <52DD06CB.8050606@ti.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Hi Tomi,
On Monday 20 January 2014 13:21:47 Tomi Valkeinen wrote:
> On 2014-01-19 23:01, Laurent Pinchart wrote:
> > Hi Tomi,
> >
> > The lcdc driver can be compiled without meram support. This is handled by
> > conditional compilation in include/video/sh_mobile_meram.h that defines
> > the
> > meram functions as stubs when meram support isn't selected.
> >
> > The problem comes from the combination of FB_SH_MOBILE_MERAM=m and
> > FB_SH_MOBILE_LCDC=y. The former makes the meram function non-stubs, while
> > the later makes the LCDC driver fail to link, as meram support is then
> > compiled as a module.
> >
> > How do you usually handle this ?
>
> I guess the easiest option is to make FB_SH_MOBILE_MERAM a bool, instead
> of tristate.
That's easy, but it would prevent meram support from being compiled as a
module when lcdc support is compiled as a module as well.
--
Regards,
Laurent Pinchart
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2014-01-20 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1385515117-23664-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
2013-11-27 1:18 ` [PATCH 13/15] fbdev: sh-mobile-lcdcfb: Enable driver compilation with COMPILE_TEST Laurent Pinchart
2013-12-11 12:51 ` Laurent Pinchart
2014-01-07 15:15 ` Laurent Pinchart
2014-01-08 8:30 ` Tomi Valkeinen
2014-01-17 9:00 ` Tomi Valkeinen
2014-01-19 21:01 ` Laurent Pinchart
2014-01-20 11:21 ` Tomi Valkeinen
2014-01-20 15:30 ` Laurent Pinchart [this message]
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=5189278.VEETF0BgjA@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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).