From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/sun4i: link in front-end code if needed
Date: Mon, 26 Feb 2018 11:53:59 +0100 [thread overview]
Message-ID: <20180226105359.k5a3rz2wow4gweba@flea.lan> (raw)
In-Reply-To: <CAK8P3a1w=hLzZLPe1TURPyyu5oxpG8yD0eb_8GrVviUODy0zqQ@mail.gmail.com>
On Mon, Feb 26, 2018 at 10:31:51AM +0100, Arnd Bergmann wrote:
> On Mon, Feb 26, 2018 at 10:21 AM, Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> > Hi,
> >
> > On Fri, Feb 23, 2018 at 02:06:52PM +0100, Arnd Bergmann wrote:
> >> When the base sun4i DRM driver is built-in but the back-end is
> >> a loadable module, we run into a link error:
> >>
> >> drivers/gpu/drm/sun4i/sun4i_drv.o: In function `sun4i_drv_probe':
> >> sun4i_drv.c:(.text+0x60c): undefined reference to `sun4i_frontend_of_table'
> >>
> >> The dependency is a bit tricky, the best workaround I have come up
> >> with is to use a Makefile hack to to interpret both
> >> CONFIG_DRM_SUN4I_BACKEND=m and CONFIG_DRM_SUN4I_BACKEND=y
> >> as a directive to build the front-end the same way as the main module.
> >>
> >> Fixes: dd0421f47505 ("drm/sun4i: Add a driver for the display frontend")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> ---
> >> drivers/gpu/drm/sun4i/Makefile | 5 ++++-
> >> 1 file changed, 4 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/sun4i/Makefile b/drivers/gpu/drm/sun4i/Makefile
> >> index 582607c0c488..db14e023256b 100644
> >> --- a/drivers/gpu/drm/sun4i/Makefile
> >> +++ b/drivers/gpu/drm/sun4i/Makefile
> >> @@ -25,6 +25,9 @@ obj-$(CONFIG_DRM_SUN4I) += sun4i-tcon.o
> >> obj-$(CONFIG_DRM_SUN4I) += sun4i_tv.o
> >> obj-$(CONFIG_DRM_SUN4I) += sun6i_drc.o
> >>
> >> -obj-$(CONFIG_DRM_SUN4I_BACKEND) += sun4i-backend.o sun4i-frontend.o
> >> +obj-$(CONFIG_DRM_SUN4I_BACKEND) += sun4i-backend.o
> >> +ifdef CONFIG_DRM_SUN4I_BACKEND
> >> +obj-$(CONFIG_DRM_SUN4I) += sun4i-frontend.o
> >> +endif
> >
> > Can we just create a Kconfig symbol, selected by DRM_SUN4I_BACKEND,
> > and we would export the symbol?
>
> Yes, I think that would work just as well. Something like
>
> config DRM_SUN4I_FRONTEND
> tristate
> default DRM_SUN4I if CONFIG_DRM_SUN4I_BACKEND != n
>
> should do the trick.
I had more something like this in mind:
https://pastebin.com/raw/XydvzAtz
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180226/b12de33e/attachment.sig>
next prev parent reply other threads:[~2018-02-26 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 13:06 [PATCH] drm/sun4i: link in front-end code if needed Arnd Bergmann
2018-02-26 9:21 ` Maxime Ripard
2018-02-26 9:31 ` Arnd Bergmann
2018-02-26 10:53 ` Maxime Ripard [this message]
2018-02-26 10:55 ` Chen-Yu Tsai
2018-03-01 9:19 ` Maxime Ripard
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=20180226105359.k5a3rz2wow4gweba@flea.lan \
--to=maxime.ripard@bootlin.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