From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH] drm: rcar-du: Fix Kconfig dependency between RCAR_DU and RCAR_MIPI_DSI
Date: Mon, 14 Nov 2022 16:21:40 +0200 [thread overview]
Message-ID: <Y3JO9NmEpS19Rt3D@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdWeZBzFM2Q8sLEqe_DfD74a1K+5qcPHADZnPfrQYqVXrg@mail.gmail.com>
Hi Geert,
On Mon, Nov 14, 2022 at 10:05:58AM +0100, Geert Uytterhoeven wrote:
> On Sun, Oct 2, 2022 at 12:06 AM Laurent Pinchart wrote:
> > When the R-Car MIPI DSI driver was added, it was a standalone encoder
> > driver without any dependency to or from the R-Car DU driver. Commit
> > 957fe62d7d15 ("drm: rcar-du: Fix DSI enable & disable sequence") then
> > added a direct call from the DU driver to the MIPI DSI driver, without
> > updating Kconfig to take the new dependency into account. Fix it the
> > same way that the LVDS encoder is handled.
> >
> > Fixes: 957fe62d7d15 ("drm: rcar-du: Fix DSI enable & disable sequence")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> Thanks for your patch, which is now commit a830a15678593948
> ("drm: rcar-du: Fix Kconfig dependency between RCAR_DU
> and RCAR_MIPI_DSI") in v6.1-rc5.
>
> > --- a/drivers/gpu/drm/rcar-du/Kconfig
> > +++ b/drivers/gpu/drm/rcar-du/Kconfig
> > @@ -44,12 +44,17 @@ config DRM_RCAR_LVDS
> > select OF_FLATTREE
> > select OF_OVERLAY
> >
> > +config DRM_RCAR_USE_MIPI_DSI
> > + bool "R-Car DU MIPI DSI Encoder Support"
> > + depends on DRM_BRIDGE && OF
> > + default DRM_RCAR_DU
>
> This means this driver is now enabled by default on systems that do not
> have the MIPI DSI Encoder (e.g. R-Car Gen2), and that we should probably
> disable it explicitly in shmobile_defconfig. Is that intentional?
I don't think so, no. Would you like to send a patch ? If so, it should
enable the option in relevant defconfig files.
> > + help
> > + Enable support for the R-Car Display Unit embedded MIPI DSI encoders.
> > +
> > config DRM_RCAR_MIPI_DSI
> > - tristate "R-Car DU MIPI DSI Encoder Support"
> > - depends on DRM && DRM_BRIDGE && OF
> > + def_tristate DRM_RCAR_DU
> > + depends on DRM_RCAR_USE_MIPI_DSI
> > select DRM_MIPI_DSI
> > - help
> > - Enable support for the R-Car Display Unit embedded MIPI DSI encoders.
> >
> > config DRM_RCAR_VSP
> > bool "R-Car DU VSP Compositor Support" if ARM
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-11-14 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 22:03 [PATCH] drm: rcar-du: Fix Kconfig dependency between RCAR_DU and RCAR_MIPI_DSI Laurent Pinchart
2022-10-03 6:52 ` Tomi Valkeinen
2022-10-03 7:01 ` Geert Uytterhoeven
2022-10-03 7:31 ` Tomi Valkeinen
2022-10-03 12:26 ` Laurent Pinchart
2022-11-14 9:05 ` Geert Uytterhoeven
2022-11-14 14:21 ` Laurent Pinchart [this message]
2022-11-14 14:52 ` Geert Uytterhoeven
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=Y3JO9NmEpS19Rt3D@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).