From: Philipp Zabel <p.zabel@pengutronix.de>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Chris Healy <cphealy@gmail.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 07/12] drm/imx: ldb: switch to drm_panel_bridge
Date: Wed, 29 May 2024 16:58:22 +0200 [thread overview]
Message-ID: <52baeec98214106ca406dd190e1b7eecd73fe255.camel@pengutronix.de> (raw)
In-Reply-To: <20240331-drm-imx-cleanup-v2-7-d81c1d1c1026@linaro.org>
On So, 2024-03-31 at 23:29 +0300, Dmitry Baryshkov wrote:
> Defer panel handling to drm_panel_bridge, unifying codepaths for the
> panel and bridge cases.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/imx/ipuv3/Kconfig | 2 ++
> drivers/gpu/drm/imx/ipuv3/imx-ldb.c | 44 ++++++++++++-------------------------
> 2 files changed, 16 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/gpu/drm/imx/ipuv3/Kconfig b/drivers/gpu/drm/imx/ipuv3/Kconfig
> index bacf0655ebaf..4e41611c8532 100644
> --- a/drivers/gpu/drm/imx/ipuv3/Kconfig
> +++ b/drivers/gpu/drm/imx/ipuv3/Kconfig
> @@ -28,7 +28,9 @@ config DRM_IMX_LDB
> tristate "Support for LVDS displays"
> depends on DRM_IMX && MFD_SYSCON
> depends on COMMON_CLK
> + depends on DRM_BRIDGE
To avoid hiding the DRM_IMX_LDB option for legacy configurations with
DRM_BRIDGE disabled, it would be better to select DRM_BRIDGE here
instead.
> select DRM_PANEL
And this shouldn't be necessary anymore.
regards
Philipp
next prev parent reply other threads:[~2024-05-29 14:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 20:28 [PATCH v2 00/12] drm/imx/ipuv3: switch LDB and parallel-display driver to use drm_bridge_connector Dmitry Baryshkov
2024-03-31 20:28 ` [PATCH v2 01/12] dt-bindings: display: fsl-imx-drm: drop edid property support Dmitry Baryshkov
2024-03-31 20:28 ` [PATCH v2 02/12] dt-bindings: display: imx/ldb: drop ddc-i2c-bus property Dmitry Baryshkov
2024-03-31 20:29 ` [PATCH v2 03/12] drm/imx: cleanup the imx-drm header Dmitry Baryshkov
2024-05-29 14:59 ` Philipp Zabel
2024-03-31 20:29 ` [PATCH v2 04/12] drm/imx: parallel-display: drop edid override support Dmitry Baryshkov
2024-05-29 14:59 ` Philipp Zabel
2024-03-31 20:29 ` [PATCH v2 05/12] drm/imx: ldb: drop custom EDID support Dmitry Baryshkov
2024-05-29 14:59 ` Philipp Zabel
2024-03-31 20:29 ` [PATCH v2 06/12] drm/imx: ldb: drop custom DDC bus support Dmitry Baryshkov
2024-05-29 15:00 ` Philipp Zabel
2024-03-31 20:29 ` [PATCH v2 07/12] drm/imx: ldb: switch to drm_panel_bridge Dmitry Baryshkov
2024-05-29 14:58 ` Philipp Zabel [this message]
2024-03-31 20:29 ` [PATCH v2 08/12] drm/imx: parallel-display: " Dmitry Baryshkov
2024-05-29 14:58 ` Philipp Zabel
2024-03-31 20:29 ` [PATCH v2 09/12] drm/imx: add internal bridge handling display-timings DT node Dmitry Baryshkov
2024-03-31 20:29 ` [PATCH v2 10/12] drm/imx: ldb: switch to imx_legacy_bridge / drm_bridge_connector Dmitry Baryshkov
2024-03-31 20:29 ` [PATCH v2 11/12] drm/imx: parallel-display: " Dmitry Baryshkov
2024-05-29 14:58 ` Philipp Zabel
2024-03-31 20:29 ` [PATCH v2 12/12] drm/imx: move imx_drm_connector_destroy to imx-tve Dmitry Baryshkov
2024-04-16 21:58 ` [PATCH v2 00/12] drm/imx/ipuv3: switch LDB and parallel-display driver to use drm_bridge_connector Dmitry Baryshkov
2024-05-27 15:40 ` Philipp Zabel
2024-05-28 0:51 ` Dmitry Baryshkov
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=52baeec98214106ca406dd190e1b7eecd73fe255.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=cphealy@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tzimmermann@suse.de \
/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).