From: Javier Martinez Canillas <javierm@redhat.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
LUU HOAI <hoai.luu.ub@renesas.com>
Subject: Re: [PATCH] drm: rcar_du: DRM_RCAR_DU optionally depends on RCAR_MIPI_DSI
Date: Thu, 3 Nov 2022 12:56:56 +0100 [thread overview]
Message-ID: <88d5165b-1825-3a71-c8c0-dd5a99cd8bf6@redhat.com> (raw)
In-Reply-To: <c9064cc6-2a9d-1094-53fb-cf56f9cbf191@redhat.com>
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
next prev parent reply other threads:[~2022-11-03 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 18:18 Randy Dunlap
2022-11-03 6:06 ` Randy Dunlap
2022-11-03 10:59 ` Kieran Bingham
2022-11-03 11:53 ` Javier Martinez Canillas
2022-11-03 11:56 ` Javier Martinez Canillas [this message]
2022-11-03 11:59 ` Kieran Bingham
2022-11-03 16:26 ` Randy Dunlap
2022-11-03 18:31 ` Javier Martinez Canillas
2022-11-09 14:11 ` Laurent Pinchart
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=88d5165b-1825-3a71-c8c0-dd5a99cd8bf6@redhat.com \
--to=javierm@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoai.luu.ub@renesas.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tomi.valkeinen+renesas@ideasonboard.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®