From: Philipp Zabel <p.zabel@pengutronix.de>
To: Wen He <wen.he_1@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: Leo Li <leoyang.li@nxp.com>
Subject: Re: [v1] gpu: ipu-v3: allow to build with ARCH_LAYERSCAPE
Date: Fri, 05 Jul 2019 12:32:04 +0200 [thread overview]
Message-ID: <1562322724.4291.5.camel@pengutronix.de> (raw)
In-Reply-To: <20190508105755.5881-1-wen.he_1@nxp.com>
Hi Wen,
On Wed, 2019-05-08 at 10:56 +0000, Wen He wrote:
> The new LS1028A DP driver code causes a link failure when DRM_IMX built-in,
> but platform is ARCH_LAYERSCAPE:
>
> drivers/gpu/drm/imx/ipuv3-crtc.c:51: undefined reference to `ipu_prg_enable'
> drivers/gpu/drm/imx/ipuv3-crtc.c:52: undefined reference to `ipu_dc_enable'
> drivers/gpu/drm/imx/ipuv3-crtc.c:53: undefined reference to `ipu_dc_enable_channel'
> drivers/gpu/drm/imx/ipuv3-crtc.c:54: undefined reference to `ipu_di_enable'
> drivers/gpu/drm/imx/ipuv3-crtc.o: In function `ipu_crtc_mode_set_nofb
>
> Adding a Kconfig dependency allow to build if ARCH_LAYERSCAPE is enable.
>
> Signed-off-by: Wen He <wen.he_1@nxp.com>
> ---
> drivers/gpu/ipu-v3/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/ipu-v3/Kconfig b/drivers/gpu/ipu-v3/Kconfig
> index fe6f8c5b4445..51ea88c440df 100644
> --- a/drivers/gpu/ipu-v3/Kconfig
> +++ b/drivers/gpu/ipu-v3/Kconfig
> @@ -1,6 +1,6 @@
> config IMX_IPUV3_CORE
> tristate "IPUv3 core support"
> - depends on SOC_IMX5 || SOC_IMX6Q || ARCH_MULTIPLATFORM || COMPILE_TEST
> + depends on SOC_IMX5 || SOC_IMX6Q || ARCH_MULTIPLATFORM || COMPILE_TEST || ARCH_LAYERSCAPE
> depends on DRM || !DRM # if DRM=m, this can't be 'y'
> select BITREVERSE
> select GENERIC_ALLOCATOR if DRM
> --
> 2.17.1
Thank you for the patch, but this does not seem right.
ipuv3-crtc.c is part of DRM_IMX, which already depends on
IMX_IPUV3_CORE. How did you manage to make it try to compile imxdrm?
Since LS1028A does not have the IPUv3, keeping this under COMPILE_TEST
should be correct.
regards
Philipp
next prev parent reply other threads:[~2019-07-05 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 10:56 Wen He
2019-07-05 10:32 ` Philipp Zabel [this message]
2019-07-09 3:11 ` [EXT] " Wen He
2019-07-23 10:29 ` Philipp Zabel
[not found] <20190508094318.25849-1-wen.he_1@nxp.com>
2019-05-08 10:33 ` Wen He
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=1562322724.4291.5.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wen.he_1@nxp.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
all inboxes | Powered by JetHome®