drm/bridge: imx8mp-hdmi-pvi: Fix build warningsTwo separate build warnings were reported. One from anuninitialized variable, and the other from returning 0instead of NULL from a pointer.Fixes:
drm/bridge: imx8mp-hdmi-pvi: Fix build warningsTwo separate build warnings were reported. One from anuninitialized variable, and the other from returning 0instead of NULL from a pointer.Fixes: 059c53e877ca ("drm/bridge: imx: add driver for HDMI TX Parallel Video Interface")Reported-by: Nathan Chancellor <nathan@kernel.org>Reported-by: kernel test robot <lkp@intel.com>Closes: https://lore.kernel.org/oe-kbuild-all/202402062134.a6CqAt3s-lkp@intel.com/Signed-off-by: Adam Ford <aford173@gmail.com>Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://lore.kernel.org/r/20240207002305.618499-1-aford173@gmail.comSigned-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20240207002305.618499-1-aford173@gmail.com
show more ...
drm/bridge: imx: add bridge wrapper driver for i.MX8MP DWC HDMIAdd a simple wrapper driver for the DWC HDMI bridge driver thatimplements the few bits that are necessary to abstract the i.MX8MPSoC
drm/bridge: imx: add bridge wrapper driver for i.MX8MP DWC HDMIAdd a simple wrapper driver for the DWC HDMI bridge driver thatimplements the few bits that are necessary to abstract the i.MX8MPSoC integration.Signed-off-by: Lucas Stach <l.stach@pengutronix.de>Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>Tested-by: Marek Vasut <marex@denx.de>Tested-by: Adam Ford <aford173@gmail.com> #imx8mp-beaconTested-by: Richard Leitner <richard.leitner@skidata.com>Tested-by: Frieder Schrempf <frieder.schrempf@kontron.de>Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>Signed-off-by: Adam Ford <aford173@gmail.com>Link: https://lore.kernel.org/r/20240203165307.7806-11-aford173@gmail.comSigned-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20240203165307.7806-11-aford173@gmail.com
drm/bridge: imx: add driver for HDMI TX Parallel Video InterfaceThis IP block is found in the HDMI subsystem of the i.MX8MP SoC. It has afull timing generator and can switch between different vide
drm/bridge: imx: add driver for HDMI TX Parallel Video InterfaceThis IP block is found in the HDMI subsystem of the i.MX8MP SoC. It has afull timing generator and can switch between different video sources. Onthe i.MX8MP however the only supported source is the LCDIF. The blockjust needs to be powered up and told about the polarity of the videosync signals to act in bypass mode.Signed-off-by: Lucas Stach <l.stach@pengutronix.de>Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>Tested-by: Marek Vasut <marex@denx.de>Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>Tested-by: Richard Leitner <richard.leitner@skidata.com>Tested-by: Frieder Schrempf <frieder.schrempf@kontron.de>Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>Tested-by: Fabio Estevam <festevam@gmail.com>Signed-off-by: Adam Ford <aford173@gmail.com>Link: https://lore.kernel.org/r/20240203165307.7806-9-aford173@gmail.comSigned-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20240203165307.7806-9-aford173@gmail.com
drm/bridge: imx93-mipi-dsi: Fix a couple of building warningsFix a couple of building warnings on used uninitialized 'best_m' and'best_n' local variables by initializing 'best_m' to zero and 'best
drm/bridge: imx93-mipi-dsi: Fix a couple of building warningsFix a couple of building warnings on used uninitialized 'best_m' and'best_n' local variables by initializing 'best_m' to zero and 'best_n'to UINT_MAX. This makes compiler happy only. No functional change.Fixes: ce62f8ea7e3f ("drm/bridge: imx: Add i.MX93 MIPI DSI support")Reported-by: kernel test robot <lkp@intel.com>Closes: https://lore.kernel.org/oe-kbuild-all/202311151746.f7u7dzbZ-lkp@intel.com/Signed-off-by: Liu Ying <victor.liu@nxp.com>Reviewed-by: Robert Foss <rfoss@kernel.org>Signed-off-by: Robert Foss <rfoss@kernel.org>Link: https://patchwork.freedesktop.org/patch/msgid/20231123051807.3818342-1-victor.liu@nxp.com
drm/bridge: imx: Add i.MX93 MIPI DSI supportFreescale i.MX93 SoC embeds a Synopsys Designware MIPI DSI hostcontroller and a Synopsys Designware MIPI DPHY. Some configurationsand extensions to th
drm/bridge: imx: Add i.MX93 MIPI DSI supportFreescale i.MX93 SoC embeds a Synopsys Designware MIPI DSI hostcontroller and a Synopsys Designware MIPI DPHY. Some configurationsand extensions to them are controlled by i.MX93 media blk-ctrl.Add a DRM bridge for i.MX93 MIPI DSI by using existing DW MIPI DSIbridge helpers and implementing i.MX93 MIPI DSI specific extensions.Signed-off-by: Liu Ying <victor.liu@nxp.com>Reviewed-by: Robert Foss <rfoss@kernel.org>Signed-off-by: Robert Foss <rfoss@kernel.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230821034008.3876938-10-victor.liu@nxp.com
drm: Explicitly include correct DT includesThe DT of_device.h and of_platform.h date back to the separateof_platform_bus_type before it as merged into the regular platform bus.As part of that mer
drm: Explicitly include correct DT includesThe DT of_device.h and of_platform.h date back to the separateof_platform_bus_type before it as merged into the regular platform bus.As part of that merge prepping Arm DT support 13 years ago, they"temporarily" include each other. They also include platform_device.hand of.h. As a result, there's a pretty much random mix of those includefiles used throughout the tree. In order to detangle these headers andreplace the implicit includes with struct declarations, users need toexplicitly include the correct includes.Signed-off-by: Rob Herring <robh@kernel.org>Acked-by: Sam Ravnborg <sam@ravnborg.org>Reviewed-by: Steven Price <steven.price@arm.com>Acked-by: Liviu Dudau <liviu.dudau@arm.com>Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>Acked-by: Robert Foss <rfoss@kernel.org>Signed-off-by: Thierry Reding <treding@nvidia.com>Link: https://patchwork.freedesktop.org/patch/msgid/20230714174545.4056287-1-robh@kernel.org
drm/bridge: imx: turn imx8{qm,qxp}-ldb into single-object modulesWith the previous fix, these modules are built from a single C file.Rename the source files so they match the module names.Signe
drm/bridge: imx: turn imx8{qm,qxp}-ldb into single-object modulesWith the previous fix, these modules are built from a single C file.Rename the source files so they match the module names.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>Reviewed-by: Liu Ying <victor.liu@nxp.com>Signed-off-by: Robert Foss <rfoss@kernel.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230605120021.1774711-2-masahiroy@kernel.org
drm/bridge: imx: fix mixed module-builtin objectWith CONFIG_DRM_IMX8QM_LDB=m and CONFIG_DRM_IMX8QXP_LDB=y (or viceversa), imx-ldb-helper.o is linked to a module and also to vmlinuxeven though the
drm/bridge: imx: fix mixed module-builtin objectWith CONFIG_DRM_IMX8QM_LDB=m and CONFIG_DRM_IMX8QXP_LDB=y (or viceversa), imx-ldb-helper.o is linked to a module and also to vmlinuxeven though the expected CFLAGS are different between builtins andmodules.This is the same situation as fixed by commit 637a642f5ca5 ("zstd:Fixing mixed module-builtin objects").Split imx-ldb-helper.c into a separate module.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>Reviewed-by: Liu Ying <victor.liu@nxp.com>Signed-off-by: Robert Foss <rfoss@kernel.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230605120021.1774711-1-masahiroy@kernel.org
drm: Use of_property_present() for testing DT property presenceIt is preferred to use typed property access functions (i.e.of_property_read_<type> functions) rather than low-levelof_get_property/
drm: Use of_property_present() for testing DT property presenceIt is preferred to use typed property access functions (i.e.of_property_read_<type> functions) rather than low-levelof_get_property/of_find_property functions for reading properties. Aspart of this, convert of_get_property/of_find_property calls to therecently added of_property_present() helper when we just want to testfor presence of a property and nothing more.Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>Reviewed-by: Liu Ying <victor.liu@nxp.com> # i.MX bridgeReviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>Link: https://lore.kernel.org/r/20230310144705.1542207-1-robh@kernel.orgSigned-off-by: Rob Herring <robh@kernel.org>
drm/bridge: imx8qxp-pxl2dpi: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possib
drm/bridge: imx8qxp-pxl2dpi: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to do error handling byreturning an error code. However the value returned is (mostly) ignoredand this typically results in resource leaks. To improve here there is aquest to make the remove callback return void. In the first step of thisquest all drivers are converted to .remove_new() which already returnsvoid.Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230318190804.234610-11-u.kleine-koenig@pengutronix.de
drm/bridge: imx8qxp-pixel-link: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's pos
drm/bridge: imx8qxp-pixel-link: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to do error handling byreturning an error code. However the value returned is (mostly) ignoredand this typically results in resource leaks. To improve here there is aquest to make the remove callback return void. In the first step of thisquest all drivers are converted to .remove_new() which already returnsvoid.Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230318190804.234610-10-u.kleine-koenig@pengutronix.de
drm/bridge: imx8qxp-pixel-combiner: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's
drm/bridge: imx8qxp-pixel-combiner: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to do error handling byreturning an error code. However the value returned is (mostly) ignoredand this typically results in resource leaks. To improve here there is aquest to make the remove callback return void. In the first step of thisquest all drivers are converted to .remove_new() which already returnsvoid.Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230318190804.234610-9-u.kleine-koenig@pengutronix.de
drm/bridge: imx8qxp-ldb: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible t
drm/bridge: imx8qxp-ldb: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to do error handling byreturning an error code. However the value returned is (mostly) ignoredand this typically results in resource leaks. To improve here there is aquest to make the remove callback return void. In the first step of thisquest all drivers are converted to .remove_new() which already returnsvoid.Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230318190804.234610-8-u.kleine-koenig@pengutronix.de
drm/bridge: imx8qm-ldb: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to
drm/bridge: imx8qm-ldb: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to do error handling byreturning an error code. However the value returned is (mostly) ignoredand this typically results in resource leaks. To improve here there is aquest to make the remove callback return void. In the first step of thisquest all drivers are converted to .remove_new() which already returnsvoid.Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20230318190804.234610-7-u.kleine-koenig@pengutronix.de
drm: Remove linux/i2c.h from drm_crtc.hdrm_crtc.h has no need for linux/i2c.h, so don't include it.Avoids useless rebuilds of the entire universe whentouching linux/i2c.h.Quite a few placs do c
drm: Remove linux/i2c.h from drm_crtc.hdrm_crtc.h has no need for linux/i2c.h, so don't include it.Avoids useless rebuilds of the entire universe whentouching linux/i2c.h.Quite a few placs do currently depend on linux/i2c.h withoutactually including it directly. All of those need to befixed up.v2: imx and mcde need linux/io.h for readl()/etc.Acked-by: Sam Ravnborg <sam@ravnborg.org>Acked-by: Jani Nikula <jani.nikula@intel.com>Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20220630195114.17407-5-ville.syrjala@linux.intel.com
drm: Remove linux/media-bus-format.h from drm_crtc.hdrm_crtc.h has no need for linux/media-bus-format.h, so don'tinclude it. Avoids useless rebuilds of the entire universe whentouching linux/medi
drm: Remove linux/media-bus-format.h from drm_crtc.hdrm_crtc.h has no need for linux/media-bus-format.h, so don'tinclude it. Avoids useless rebuilds of the entire universe whentouching linux/media-bus-format.h.Quite a few placs do currently depend on linux/media-bus-format.hwithout actually including it directly. All of those need to befixed up.v2: Deal with ingenic as wellv3: Fix up mxsfb and remaining parts of imxAcked-by: Sam Ravnborg <sam@ravnborg.org>Acked-by: Jani Nikula <jani.nikula@intel.com>Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>Link: https://patchwork.freedesktop.org/patch/msgid/20220630195114.17407-4-ville.syrjala@linux.intel.com
drm/bridge: imx: i.MX8 bridge drivers should depend on ARCH_MXCThe various Freescale i.MX8 display bridges are only present onFreescale i.MX8 SoCs. Hence add a dependency on ARCH_MXC, to prevent
drm/bridge: imx: i.MX8 bridge drivers should depend on ARCH_MXCThe various Freescale i.MX8 display bridges are only present onFreescale i.MX8 SoCs. Hence add a dependency on ARCH_MXC, to preventasking the user about these drivers when configuring a kernel withouti.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>Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>Link: https://patchwork.freedesktop.org/patch/msgid/42c542b53a1c8027b23a045045fbb7b34479913d.1656072500.git.geert+renesas@glider.be
drm/bridge: imx: Add LDB support for i.MX8qmThis patch adds a drm bridge driver for i.MX8qm LVDS display bridge(LDB)which is officially named as pixel mapper. The LDB has two channels.Each of th
drm/bridge: imx: Add LDB support for i.MX8qmThis patch adds a drm bridge driver for i.MX8qm LVDS display bridge(LDB)which is officially named as pixel mapper. The LDB has two channels.Each of them supports up to 30bpp parallel input color format and canmap the input to VESA or JEIDA standards. The two channels can be usedsimultaneously, either in dual mode or split mode. In dual mode, thetwo channels output identical data. In split mode, channel0 outputsodd pixels and channel1 outputs even pixels. This patch supports theLDB single mode and split mode.Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Colibri iMX8X, LT170410-2WHC, LP156WF1Reviewed-by: Robert Foss <robert.foss@linaro.org>Signed-off-by: Liu Ying <victor.liu@nxp.com>Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>Signed-off-by: Robert Foss <robert.foss@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20220611141421.718743-13-victor.liu@nxp.com
drm/bridge: imx: Add LDB support for i.MX8qxpThis patch adds a drm bridge driver for i.MX8qxp LVDS display bridge(LDB)which is officially named as pixel mapper. The LDB has two channels.Each of
drm/bridge: imx: Add LDB support for i.MX8qxpThis patch adds a drm bridge driver for i.MX8qxp LVDS display bridge(LDB)which is officially named as pixel mapper. The LDB has two channels.Each of them supports up to 24bpp parallel input color format and can mapthe input to VESA or JEIDA standards. The two channels cannot be usedsimultaneously, that is to say, the user should pick one of them to use.Two LDB channels from two LDB instances can work together in LDB splitmode to support a dual link LVDS display. The channel indexes have to bedifferent. Channel0 outputs odd pixels and channel1 outputs even pixels.This patch supports the LDB single mode and split mode.Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Colibri iMX8X, LT170410-2WHC, LP156WF1Reviewed-by: Robert Foss <robert.foss@linaro.org>Signed-off-by: Liu Ying <victor.liu@nxp.com>Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>Signed-off-by: Robert Foss <robert.foss@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20220611141421.718743-12-victor.liu@nxp.com
drm/bridge: imx: Add LDB driver helper supportThis patch adds a helper to support LDB drm bridge drivers fori.MX SoCs. Helper functions supported by this helper shouldimplement common logics for
drm/bridge: imx: Add LDB driver helper supportThis patch adds a helper to support LDB drm bridge drivers fori.MX SoCs. Helper functions supported by this helper shouldimplement common logics for all LDB modules embedded in i.MX SoCs.Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Colibri iMX8X, LT170410-2WHC, LP156WF1Reviewed-by: Robert Foss <robert.foss@linaro.org>Signed-off-by: Liu Ying <victor.liu@nxp.com>Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>Signed-off-by: Robert Foss <robert.foss@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20220611141421.718743-10-victor.liu@nxp.com
drm/bridge: imx: Add i.MX8qxp pixel link to DPI supportThis patch adds a drm bridge driver for i.MX8qxp pixel link to displaypixel interface(PXL2DPI). The PXL2DPI interfaces the pixel link 36-bit
drm/bridge: imx: Add i.MX8qxp pixel link to DPI supportThis patch adds a drm bridge driver for i.MX8qxp pixel link to displaypixel interface(PXL2DPI). The PXL2DPI interfaces the pixel link 36-bitdata output and the DSI controller’s MIPI-DPI 24-bit data input, andinputs of LVDS Display Bridge(LDB) module used in LVDS mode, to remapthe pixel color codings between those modules. The PXL2DPI is purelycombinatorial.Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Colibri iMX8X, LT170410-2WHC, LP156WF1Reviewed-by: Robert Foss <robert.foss@linaro.org>Signed-off-by: Liu Ying <victor.liu@nxp.com>Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>Signed-off-by: Robert Foss <robert.foss@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20220611141421.718743-9-victor.liu@nxp.com
drm/bridge: imx: Add i.MX8qm/qxp display pixel link supportThis patch adds a drm bridge driver for i.MX8qm/qxp display pixel link.The pixel link forms a standard asynchronous linkage betweenpixel
drm/bridge: imx: Add i.MX8qm/qxp display pixel link supportThis patch adds a drm bridge driver for i.MX8qm/qxp display pixel link.The pixel link forms a standard asynchronous linkage betweenpixel sources(display controller or camera module) and pixelconsumers(imaging or displays). It consists of two distinctfunctions, a pixel transfer function and a control interface.Reviewed-by: Robert Foss <robert.foss@linaro.org>Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Colibri iMX8X, LT170410-2WHC, LP156WF1Signed-off-by: Liu Ying <victor.liu@nxp.com>Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>Signed-off-by: Robert Foss <robert.foss@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20220611141421.718743-7-victor.liu@nxp.com
drm/bridge: imx: Add i.MX8qm/qxp pixel combiner supportThis patch adds a drm bridge driver for i.MX8qm/qxp pixel combiner.The pixel combiner takes two output streams from a single displaycontroll
drm/bridge: imx: Add i.MX8qm/qxp pixel combiner supportThis patch adds a drm bridge driver for i.MX8qm/qxp pixel combiner.The pixel combiner takes two output streams from a single displaycontroller and manipulates the two streams to support a numberof modes(bypass, pixel combine, YUV444 to YUV422, split_RGB) configuredas either one screen, two screens, or virtual screens. The pixelcombiner is also responsible for generating some of the control signalsfor the pixel link output channel. For now, the driver only supportsthe bypass mode.Reviewed-by: Robert Foss <robert.foss@linaro.org>Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Colibri iMX8X, LT170410-2WHC, LP156WF1Signed-off-by: Liu Ying <victor.liu@nxp.com>Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>Signed-off-by: Robert Foss <robert.foss@linaro.org>Link: https://patchwork.freedesktop.org/patch/msgid/20220611141421.718743-5-victor.liu@nxp.com
12