mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liu Ying <victor.liu@nxp.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Robert Foss <robert.foss@linaro.org>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Marek Vasut <marex@denx.de>
Cc: dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/bridge: imx: i.MX8 bridge drivers should depend on ARCH_MXC
Date: Tue, 28 Jun 2022 10:31:32 +0800	[thread overview]
Message-ID: <9f5b511708ca9b30ef101a46a5d1b76f03b2c4fc.camel@nxp.com> (raw)
In-Reply-To: <b625ba83-fee9-b668-09db-976cb3bef3ca@baylibre.com>

On Mon, 2022-06-27 at 14:22 +0200, Neil Armstrong wrote:
> Hi,

Hi,

> 
> On 24/06/2022 14:10, Geert Uytterhoeven wrote:
> > The various Freescale i.MX8 display bridges are only present on
> > Freescale i.MX8 SoCs.  Hence add a dependency on ARCH_MXC, to
> > prevent
> > asking the user about these drivers when configuring a kernel
> > without
> > i.MX SoC support.
> > 
> > Fixes: e60c4354840b2fe8 ("drm/bridge: imx: Add LDB support for
> > i.MX8qm")
> > Fixes: 3818715f62b42b5c ("drm/bridge: imx: Add LDB support for
> > i.MX8qxp")
> > Fixes: 96988a526c97cfbe ("drm/bridge: imx: Add i.MX8qxp pixel link
> > to DPI support")
> > Fixes: 1ec17c26bc06289d ("drm/bridge: imx: Add i.MX8qm/qxp display
> > pixel link support")
> > Fixes: 93e163a9e0392aca ("drm/bridge: imx: Add i.MX8qm/qxp pixel
> > combiner support")
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > Reviewed-by: Liu Ying <victor.liu@nxp.com>
> > ---
> > v2:
> >    - s/i.MX8MP/i.MX8/,
> >    - Add Reviewed-by.
> > ---
> >   drivers/gpu/drm/bridge/imx/Kconfig | 4 ++++
> >   1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/bridge/imx/Kconfig
> > b/drivers/gpu/drm/bridge/imx/Kconfig
> > index 212a7b0e64fd8b5a..608f47f41bcd1c81 100644
> > --- a/drivers/gpu/drm/bridge/imx/Kconfig
> > +++ b/drivers/gpu/drm/bridge/imx/Kconfig
> > @@ -1,3 +1,5 @@
> > +if ARCH_MXC || COMPILE_TEST
> > +
> >   config DRM_IMX8QM_LDB
> >   	tristate "Freescale i.MX8QM LVDS display bridge"
> >   	depends on OF
> > @@ -41,3 +43,5 @@ config DRM_IMX8QXP_PIXEL_LINK_TO_DPI
> >   	help
> >   	  Choose this to enable pixel link to display pixel
> > interface(PXL2DPI)
> >   	  found in Freescale i.MX8qxp processor.
> > +
> > +endif # ARCH_MXC || COMPILE_TEST
> 
> I was wondering why those were added in drivers/gpu/drm/bridge/imx
> since they are specific to NXP SoCs,
> I think they should be moved in the right drm imx subsystem instead
> of this change.

There are 2 directories which contain display controller drivers for
i.MX SoCs:
a. drivers/gpu/drm/imx - i.MX51/53/6qdl IPUv3, i.MX8mq DCSS and
   i.MX8qm/qxp DPU([1], not landed yet)
b. drivers/gpu/drm/mxsfb - i.MX23/28/6sx/8mq LCDIF and i.MX8mp
   LCDIFv3([2], not landed yet)

Bridges added in drivers/gpu/drm/bridge/imx make it possible to share
bridge drivers across display controllers.  I see chance to use the
LVDS Display Bridge(LDB) helper(imx-ldb-helper.c) for i.MX6sx LDB.

[1] 
https://patchwork.kernel.org/project/dri-devel/patch/20220407091156.1211923-6-victor.liu@nxp.com/
[2] 
https://patchwork.kernel.org/project/dri-devel/patch/20220624180201.150417-2-marex@denx.de/

Regards,
Liu Ying


  reply	other threads:[~2022-06-28  2:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 12:10 Geert Uytterhoeven
2022-06-27 12:22 ` Neil Armstrong
2022-06-28  2:31   ` Liu Ying [this message]
2022-06-28  7:10     ` Neil Armstrong
2022-07-01  7:09       ` Liu Ying
2022-07-01  8:29 ` Neil Armstrong

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=9f5b511708ca9b30ef101a46a5d1b76f03b2c4fc.camel@nxp.com \
    --to=victor.liu@nxp.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=andrzej.hajda@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=narmstrong@baylibre.com \
    --cc=robert.foss@linaro.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnguo@kernel.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: 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®