From: Jagan Teki <jagan@amarulasolutions.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Inki Dae <inki.dae@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Neil Armstrong <narmstrong@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: Marek Vasut <marex@denx.de>,
linux-samsung-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-amarula <linux-amarula@amarulasolutions.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: [PATCH v10 0/3] drm: exynos: dsi: Restore the bridge chain
Date: Mon, 12 Dec 2022 20:25:05 +0530 [thread overview]
Message-ID: <20221212145508.15096-1-jagan@amarulasolutions.com> (raw)
Split the Exynos DSI bridge chain update patches from Samsung DSIM
bridge driver for easy to apply.
Changes for v10:
- collect Marek.V Review tag
Any inputs?
Jagan.
Jagan Teki (1):
drm: panel: Enable prepare_prev_first flag for samsung-s6e panels
Marek Szyprowski (2):
drm/bridge: tc358764: Enable pre_enable_prev_first flag
drm: exynos: dsi: Restore proper bridge chain order
drivers/gpu/drm/bridge/tc358764.c | 1 +
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 8 ++++++--
drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c | 1 +
drivers/gpu/drm/panel/panel-samsung-s6e63j0x03.c | 1 +
drivers/gpu/drm/panel/panel-samsung-s6e8aa0.c | 1 +
5 files changed, 10 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2022-12-12 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 14:55 Jagan Teki [this message]
2022-12-12 14:55 ` [PATCH v10 1/3] drm: panel: Enable prepare_prev_first flag for samsung-s6e panels Jagan Teki
2022-12-12 14:55 ` [PATCH v10 2/3] drm/bridge: tc358764: Enable pre_enable_prev_first flag Jagan Teki
2022-12-12 14:55 ` [PATCH v10 3/3] drm: exynos: dsi: Restore proper bridge chain order Jagan Teki
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=20221212145508.15096-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=marex@denx.de \
--cc=narmstrong@linaro.org \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=sw0312.kim@samsung.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