From: Geert Uytterhoeven <geert@linux-m68k.org> To: Randy Dunlap <rdunlap@infradead.org> Cc: dri-devel <dri-devel@lists.freedesktop.org>, LKML <linux-kernel@vger.kernel.org>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Kieran Bingham <kieran.bingham@ideasonboard.com>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Koji Matsuoka <koji.matsuoka.xm@renesas.com>, David Airlie <airlied@linux.ie> Subject: Re: [RFC PATCH] drm: rcar-du: make all sub-symbols depend on DRM_RCAR_DU Date: Fri, 6 Mar 2020 09:00:12 +0100 [thread overview] Message-ID: <CAMuHMdV8pKP3_6sO+BSyqde9J_qkac7+nc8RnTZwOuphqAnTSQ@mail.gmail.com> (raw) In-Reply-To: <4b50cc9f-1434-b78a-d56a-fadfd030f002@infradead.org> Hi Randy, Thanks for your patch! On Fri, Mar 6, 2020 at 4:18 AM Randy Dunlap <rdunlap@infradead.org> wrote: > From: Randy Dunlap <rdunlap@infradead.org> > > DRM_RCAR_CMM depends on DRM_RCAR_DU. Since the following Kconfig > symbols do not depend on DRM_RCAR_DU, the menu presentation is > broken for these and following non-R-Car Kconfig symbols. > > Is it safe/appropriate to make all of these symbols depend on > DRM_RCAR_DU? It make the kconfig menu presentation much cleaner. I think it is. But I'd use a big "#if DRM_RCAR_DU" block instead of individual dependencies. > Signed-off-by: Randy Dunlap <rdunlap@infradead.org> > --- linux-next-20200305.orig/drivers/gpu/drm/rcar-du/Kconfig > +++ linux-next-20200305/drivers/gpu/drm/rcar-du/Kconfig > @@ -24,6 +24,7 @@ config DRM_RCAR_CMM > config DRM_RCAR_DW_HDMI > tristate "R-Car DU Gen3 HDMI Encoder Support" > depends on DRM && OF > + depends on DRM_RCAR_DU > select DRM_DW_HDMI > help > Enable support for R-Car Gen3 internal HDMI encoder. > @@ -31,6 +32,7 @@ config DRM_RCAR_DW_HDMI > config DRM_RCAR_LVDS > tristate "R-Car DU LVDS Encoder Support" > depends on DRM && DRM_BRIDGE && OF > + depends on DRM_RCAR_DU > select DRM_PANEL > select OF_FLATTREE > select OF_OVERLAY > @@ -47,4 +49,5 @@ config DRM_RCAR_VSP > > config DRM_RCAR_WRITEBACK > bool > + depends on DRM_RCAR_DU > default y if ARM64 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Randy Dunlap <rdunlap@infradead.org> Cc: David Airlie <airlied@linux.ie>, LKML <linux-kernel@vger.kernel.org>, Koji Matsuoka <koji.matsuoka.xm@renesas.com>, dri-devel <dri-devel@lists.freedesktop.org>, Kieran Bingham <kieran.bingham@ideasonboard.com>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Laurent Pinchart <laurent.pinchart@ideasonboard.com> Subject: Re: [RFC PATCH] drm: rcar-du: make all sub-symbols depend on DRM_RCAR_DU Date: Fri, 6 Mar 2020 09:00:12 +0100 [thread overview] Message-ID: <CAMuHMdV8pKP3_6sO+BSyqde9J_qkac7+nc8RnTZwOuphqAnTSQ@mail.gmail.com> (raw) In-Reply-To: <4b50cc9f-1434-b78a-d56a-fadfd030f002@infradead.org> Hi Randy, Thanks for your patch! On Fri, Mar 6, 2020 at 4:18 AM Randy Dunlap <rdunlap@infradead.org> wrote: > From: Randy Dunlap <rdunlap@infradead.org> > > DRM_RCAR_CMM depends on DRM_RCAR_DU. Since the following Kconfig > symbols do not depend on DRM_RCAR_DU, the menu presentation is > broken for these and following non-R-Car Kconfig symbols. > > Is it safe/appropriate to make all of these symbols depend on > DRM_RCAR_DU? It make the kconfig menu presentation much cleaner. I think it is. But I'd use a big "#if DRM_RCAR_DU" block instead of individual dependencies. > Signed-off-by: Randy Dunlap <rdunlap@infradead.org> > --- linux-next-20200305.orig/drivers/gpu/drm/rcar-du/Kconfig > +++ linux-next-20200305/drivers/gpu/drm/rcar-du/Kconfig > @@ -24,6 +24,7 @@ config DRM_RCAR_CMM > config DRM_RCAR_DW_HDMI > tristate "R-Car DU Gen3 HDMI Encoder Support" > depends on DRM && OF > + depends on DRM_RCAR_DU > select DRM_DW_HDMI > help > Enable support for R-Car Gen3 internal HDMI encoder. > @@ -31,6 +32,7 @@ config DRM_RCAR_DW_HDMI > config DRM_RCAR_LVDS > tristate "R-Car DU LVDS Encoder Support" > depends on DRM && DRM_BRIDGE && OF > + depends on DRM_RCAR_DU > select DRM_PANEL > select OF_FLATTREE > select OF_OVERLAY > @@ -47,4 +49,5 @@ config DRM_RCAR_VSP > > config DRM_RCAR_WRITEBACK > bool > + depends on DRM_RCAR_DU > default y if ARM64 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-06 8:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-06 3:17 [RFC PATCH] drm: rcar-du: make all sub-symbols depend on DRM_RCAR_DU Randy Dunlap 2020-03-06 3:17 ` Randy Dunlap 2020-03-06 8:00 ` Geert Uytterhoeven [this message] 2020-03-06 8:00 ` Geert Uytterhoeven 2020-03-06 14:28 ` Laurent Pinchart 2020-03-06 14:28 ` Laurent Pinchart 2020-03-06 15:09 ` Randy Dunlap 2020-03-06 15:09 ` Randy Dunlap
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=CAMuHMdV8pKP3_6sO+BSyqde9J_qkac7+nc8RnTZwOuphqAnTSQ@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=airlied@linux.ie \ --cc=dri-devel@lists.freedesktop.org \ --cc=kieran.bingham@ideasonboard.com \ --cc=koji.matsuoka.xm@renesas.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=rdunlap@infradead.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.