From: Maxime Ripard <mripard@kernel.org>
To: dri-devel@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>,
Javier Martinez Canillas <javierm@redhat.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: [PATCH 2/3] drm/todo: Create a TODO item for MIPI-DSI rework
Date: Wed, 12 Jun 2024 16:35:52 +0200 [thread overview]
Message-ID: <20240612143553.915966-2-mripard@kernel.org> (raw)
In-Reply-To: <20240612143553.915966-1-mripard@kernel.org>
The MIPI-DSI infrastructure and setup we have so far is limited and
doesn't provide a good way to address some corner-cases.
Add a TODO entry to document what is needed.
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
Documentation/gpu/todo.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
index 52fd8672fb6d..94139c652663 100644
--- a/Documentation/gpu/todo.rst
+++ b/Documentation/gpu/todo.rst
@@ -633,10 +633,30 @@ long as that supports DMA. Otherwise importing can still needlessly fail.
Contact: Thomas Zimmermann <tzimmermann@suse.de>, Daniel Vetter
Level: Advanced
+Improve MIPI-DSI infrastructure
+-------------------------------
+
+The MIPI-DSI infrastructure in KMS supports MIPI-DSI devices in part
+through a dedicated bus (`drm_mipi_dsi.c`) and in part through ad-hoc
+calls in drivers, especially to handle the power state of the bus.
+
+This is an oddity as far as the device model is concerned, but is also
+an issue when multiple devices are chained (like bridges) and have
+different requirements.
+
+It would be a good idea to move all the power state handling out of KMS
+and into the bus support itself.
+
+See `[RFC PATCH 03/10] drm/mipi-dsi: add API for manual control over the DSI link power state <https://lore.kernel.org/dri-devel/20231016165355.1327217-4-dmitry.baryshkov@linaro.org/>`_
+
+Contact: Maxime Ripard <mripard@kernel.org>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
+
+Level: Advanced
+
Improve HDMI Infrastructure
---------------------------
We have a bunch of helpers to handle HDMI and reduce the boilerplate in
drivers. Support so far includes HDMI 1.4 support, but we need to extend
--
2.45.2
next prev parent reply other threads:[~2024-06-12 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 14:35 [PATCH 1/3] drm/todo: Create a TODO item for additional HDMI work Maxime Ripard
2024-06-12 14:35 ` Maxime Ripard [this message]
2024-06-12 14:35 ` [PATCH 3/3] drm/todo: Add TODO entry for "lints" Maxime Ripard
2024-06-12 18:49 ` Dmitry Baryshkov
2024-06-12 16:11 ` [PATCH 1/3] drm/todo: Create a TODO item for additional HDMI work Dmitry Baryshkov
2024-06-13 7:44 ` Jani Nikula
2024-06-20 13:33 ` Maxime Ripard
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=20240612143553.915966-2-mripard@kernel.org \
--to=mripard@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.