[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <88d5165b-1825-3a71-c8c0-dd5a99cd8bf6@redhat.com>
Date: Thu, 3 Nov 2022 12:56:56 +0100
From: Javier Martinez Canillas <javierm@...hat.com>
To: Kieran Bingham <kieran.bingham+renesas@...asonboard.com>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org
Cc: Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
dri-devel@...ts.freedesktop.org, linux-renesas-soc@...r.kernel.org,
Tomi Valkeinen <tomi.valkeinen+renesas@...asonboard.com>,
LUU HOAI <hoai.luu.ub@...esas.com>
Subject: Re: [PATCH] drm: rcar_du: DRM_RCAR_DU optionally depends on
RCAR_MIPI_DSI
On 11/3/22 12:53, Javier Martinez Canillas wrote:
[...]
>>
>
> What this Kconfig expression is saying is that it depends on DRM_RCAR_MIPI_DSI=y
> if DRM_RCAR_DU=y and DRM_RCAR_MIPI_DSI=m if DRM_RCAR_DU=m. But that the it can
It should had been s/and/or here but you get the idea.
> also be satisfied if is not set DRM_RCAR_MIPI_DSI.
>
> This is usually used to make sure that you don't end with a configuration where
> DRM_RCAR_MIPI_DSI=y and DRM_RCAR_DU=m or DRM_RCAR_MIPI_DSI=m and DRM_RCAR_DU=y.
>
> Randy, I think that it's more idiomatic though to it express as following:
>
> depends on DRM_RCAR_MIPI_DSI || !DRM_RCAR_MIPI_DSI
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
Powered by blists - more mailing lists