From: Jackie Liu <liu.yun@linux.dev>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
laurent.pinchart@ideasonboard.com,
dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, liuyun01@kylinos.cn,
kieran.bingham+renesas@ideasonboard.com
Subject: Re: [PATCH] drm: rcar-du: crtc: force depends on cmm
Date: Wed, 28 Jul 2021 17:57:26 +0800 [thread overview]
Message-ID: <1dd90e70-c2d3-e13f-832a-505c91e1898e@linux.dev> (raw)
In-Reply-To: <ca54fd2a-0436-d12a-5d90-bc3ff0b691b7@ideasonboard.com>
Hi Kieran.
How about this.
diff --git a/drivers/gpu/drm/rcar-du/Kconfig
b/drivers/gpu/drm/rcar-du/Kconfig
index b47e74421e34..14cf3e6415d7 100644
--- a/drivers/gpu/drm/rcar-du/Kconfig
+++ b/drivers/gpu/drm/rcar-du/Kconfig
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
config DRM_RCAR_DU
tristate "DRM Support for R-Car Display Unit"
- depends on DRM && OF
+ depends on DRM && OF && m
depends on ARM || ARM64
depends on ARCH_RENESAS || COMPILE_TEST
imply DRM_RCAR_CMM
Of course, this is not a good way, in fact, as long as rcar-du built-in,
cmm must also be built-in, otherwise an error will be reported.
Do you have a good way?
Thanks, Jackie.
在 2021/7/28 下午4:58, Kieran Bingham 写道:
> Hi Jackie,
>
> On 28/07/2021 09:42, Jackie Liu wrote:
>> From: Jackie Liu <liuyun01@kylinos.cn>
>>
>> After the patch 78b6bb1d24db ("drm: rcar-du: crtc: Control CMM operations"),
>> the cmm module must be included in the crtc. We cannot remove this
>> configuration option separately. Therefore, simply linking them together
>> is the best solution, otherwise some errors will be reported.
>>
>
> Yikes, I'm sure we've had plenty of problems with the config options on
> this module. The churn alone makes me wonder if it should just be part
> of the overall module to simplify things... but...
>
>> rcar_du_crtc.c:(.text+0x194): undefined reference to `rcar_cmm_setup'
>> rcar_du_crtc.c:(.text+0x11bc): undefined reference to `rcar_cmm_enable'
>> rcar_du_crtc.c:(.text+0x1604): undefined reference to `rcar_cmm_disable'
>> rcar_du_kms.c:(.text+0x768): undefined reference to `rcar_cmm_init'
>
> Those are guarded by #if IS_ENABLED in the header.
>
> So from that - perhaps we can assume that the config attempted here was
> a built-in DU - but a module CMM which wouldn't be supported?
>
>
>
>> Fixes: 78b6bb1d24db ("rm: rcar-du: crtc: Control CMM operations")
>
> That fixes tag is missing a 'd', but that's trivial.
>
>
>> Reported-by: kernel-bot <k2ci@kylinos.cn>
>> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
>> ---
>> drivers/gpu/drm/rcar-du/Kconfig | 8 --------
>> drivers/gpu/drm/rcar-du/Makefile | 2 +-
>> 2 files changed, 1 insertion(+), 9 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/rcar-du/Kconfig b/drivers/gpu/drm/rcar-du/Kconfig
>> index b47e74421e34..bc71ad2a472f 100644
>> --- a/drivers/gpu/drm/rcar-du/Kconfig
>> +++ b/drivers/gpu/drm/rcar-du/Kconfig
>> @@ -4,7 +4,6 @@ config DRM_RCAR_DU
>> depends on DRM && OF
>> depends on ARM || ARM64
>> depends on ARCH_RENESAS || COMPILE_TEST
>> - imply DRM_RCAR_CMM
>> imply DRM_RCAR_LVDS
>> select DRM_KMS_HELPER
>> select DRM_KMS_CMA_HELPER
>> @@ -14,13 +13,6 @@ config DRM_RCAR_DU
>> Choose this option if you have an R-Car chipset.
>> If M is selected the module will be called rcar-du-drm.
>>
>> -config DRM_RCAR_CMM
>> - tristate "R-Car DU Color Management Module (CMM) Support"
>> - depends on DRM && OF
>> - depends on DRM_RCAR_DU
>> - help
>> - Enable support for R-Car Color Management Module (CMM).
>> -
>
> I suspect the issue lies somewhere in this config that the CMM is not
> being enforced to be a built in when the DU is built in ?
>
>
>> config DRM_RCAR_DW_HDMI
>> tristate "R-Car Gen3 and RZ/G2 DU HDMI Encoder Support"
>> depends on DRM && OF
>> diff --git a/drivers/gpu/drm/rcar-du/Makefile b/drivers/gpu/drm/rcar-du/Makefile
>> index 4d1187ccc3e5..76ff2e15bc2d 100644
>> --- a/drivers/gpu/drm/rcar-du/Makefile
>> +++ b/drivers/gpu/drm/rcar-du/Makefile
>> @@ -5,6 +5,7 @@ rcar-du-drm-y := rcar_du_crtc.o \
>> rcar_du_group.o \
>> rcar_du_kms.o \
>> rcar_du_plane.o \
>> + rcar_cmm.o
>>
>> rcar-du-drm-$(CONFIG_DRM_RCAR_LVDS) += rcar_du_of.o \
>> rcar_du_of_lvds_r8a7790.dtb.o \
>> @@ -15,7 +16,6 @@ rcar-du-drm-$(CONFIG_DRM_RCAR_LVDS) += rcar_du_of.o \
>> rcar-du-drm-$(CONFIG_DRM_RCAR_VSP) += rcar_du_vsp.o
>> rcar-du-drm-$(CONFIG_DRM_RCAR_WRITEBACK) += rcar_du_writeback.o
>>
>> -obj-$(CONFIG_DRM_RCAR_CMM) += rcar_cmm.o
>> obj-$(CONFIG_DRM_RCAR_DU) += rcar-du-drm.o
>> obj-$(CONFIG_DRM_RCAR_DW_HDMI) += rcar_dw_hdmi.o
>> obj-$(CONFIG_DRM_RCAR_LVDS) += rcar_lvds.o
>>
next prev parent reply other threads:[~2021-07-28 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 8:42 [PATCH] drm: rcar-du: crtc: force depends on cmm Jackie Liu
2021-07-28 8:58 ` Kieran Bingham
2021-07-28 9:34 ` Jackie Liu
2021-07-28 10:46 ` Kieran Bingham
2021-07-28 10:55 ` Laurent Pinchart
2021-07-28 9:57 ` Jackie Liu [this message]
2021-07-28 11:09 ` Kieran Bingham
2021-07-28 11:30 ` Laurent Pinchart
2021-07-28 12:13 ` Kieran Bingham
2021-07-28 12:21 ` Jackie Liu
2021-07-28 12:24 ` Kieran Bingham
2021-07-28 12:28 ` Jackie Liu
2021-07-28 12:14 ` Jackie Liu
2021-07-28 19:34 ` kernel test robot
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=1dd90e70-c2d3-e13f-832a-505c91e1898e@linux.dev \
--to=liu.yun@linux.dev \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=liuyun01@kylinos.cn \
/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).