From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: YueHaibing <yuehaibing@huawei.com>, <airlied@linux.ie>,
<daniel@ffwll.ch>, <tzimmermann@suse.de>,
<dmitry.baryshkov@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 -next] drm/display: Fix build error without CONFIG_OF
Date: Fri, 6 May 2022 08:52:08 -0700 [thread overview]
Message-ID: <df0fd0ea-96db-ec4c-2271-280bd8bcdf79@quicinc.com> (raw)
In-Reply-To: <20220506123246.21788-1-yuehaibing@huawei.com>
On 5/6/2022 5:32 AM, YueHaibing wrote:
> While CONFIG_OF is n but COMPILE_TEST is y, we got this:
>
> WARNING: unmet direct dependencies detected for DRM_DP_AUX_BUS
> Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && OF [=n]
> Selected by [y]:
> - DRM_MSM [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARCH_QCOM || SOC_IMX5 || COMPILE_TEST [=y]) && COMMON_CLK [=y] && IOMMU_SUPPORT [=y] && (QCOM_OCMEM [=n] || QCOM_OCMEM [=n]=n) && (QCOM_LLCC [=y] || QCOM_LLCC [=y]=n) && (QCOM_COMMAND_DB [=n] || QCOM_COMMAND_DB [=n]=n)
>
> Make DRM_DP_AUX_BUS depends on OF || COMPILE_TEST to fix this warning.
>
> Fixes: f5d01644921b ("drm/msm: select DRM_DP_AUX_BUS for the AUX bus support")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> ---
> v2: fix this in DRM_DP_AUX_BUS dependencies
> ---
> drivers/gpu/drm/display/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/display/Kconfig b/drivers/gpu/drm/display/Kconfig
> index 1b6e6af37546..09712b88a5b8 100644
> --- a/drivers/gpu/drm/display/Kconfig
> +++ b/drivers/gpu/drm/display/Kconfig
> @@ -3,7 +3,7 @@
> config DRM_DP_AUX_BUS
> tristate
> depends on DRM
> - depends on OF
> + depends on OF || COMPILE_TEST
>
> config DRM_DISPLAY_HELPER
> tristate
next prev parent reply other threads:[~2022-05-06 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 12:32 YueHaibing
2022-05-06 13:01 ` Dmitry Baryshkov
2022-05-06 15:52 ` Abhinav Kumar [this message]
2022-05-21 2:43 ` YueHaibing
2022-05-23 12:46 ` Linus Walleij
2022-05-23 12:54 ` Linus Walleij
2022-05-23 12:57 ` Dmitry Baryshkov
2022-05-25 13:36 ` Dmitry Baryshkov
2022-05-26 20:08 ` Linus Walleij
2022-05-27 9:56 ` Dmitry Baryshkov
2022-05-26 15:02 ` Dmitry Baryshkov
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=df0fd0ea-96db-ec4c-2271-280bd8bcdf79@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=yuehaibing@huawei.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®