linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 00/10] drm/bridge: Make panel and bridge probe order consistent
@ 2021-07-20 13:45 Maxime Ripard
  2021-07-20 13:45 ` [PATCH 01/10] Revert "drm/vc4: dsi: Only register our component once a DSI device is attached" Maxime Ripard
                   ` (9 more replies)
  0 siblings, 10 replies; 22+ messages in thread
From: Maxime Ripard @ 2021-07-20 13:45 UTC (permalink / raw)
  To: Robert Foss, Andrzej Hajda, Daniel Vetter, David Airlie,
	Sam Ravnborg, Maarten Lankhorst, Thomas Zimmermann,
	Maxime Ripard, Neil Armstrong, Jonas Karlman, Jernej Skrabec,
	Thierry Reding, Laurent Pinchart
  Cc: dri-devel, linux-kernel

Hi,\r
\r
We've encountered an issue with the RaspberryPi DSI panel that prevented the\r
whole display driver from probing.\r
\r
The issue is described in detail in the commit 7213246a803f ("drm/vc4: dsi:\r
Only register our component once a DSI device is attached"), but the basic idea\r
is that since the panel is probed through i2c, there's no synchronization\r
between its probe and the registration of the MIPI-DSI host it's attached to.\r
\r
We initially moved the component framework registration to the MIPI-DSI Host\r
attach hook to make sure we register our component only when we have a DSI\r
device attached to our MIPI-DSI host, and then use lookup our DSI device in our\r
bind hook.\r
\r
However, all the DSI bridges controlled through i2c are only registering their\r
associated DSI device in their bridge attach hook, meaning with our change\r
above, we never got that far, and therefore ended up in the same situation than\r
the one we were trying to fix for panels.\r
\r
Since the RaspberryPi panel is the only driver in that situation, whereas it\r
seems like there's a consensus in bridge drivers, it makes more sense to try to\r
mimic the bridge pattern in the panel driver.\r
\r
However, panels don't have an attach hook, and adding more panel hooks would\r
lead to more path to maintain in each and every driver, while the general push\r
is towards bridges. We also have to make sure that each and every DSI host and\r
device driver behaves the same in order to have expectations to rely on.\r
\r
The solution I'm proposing is thus done in several steps:\r
\r
  - We get rid of the initial patch to make sure we support the bridge case,\r
    and not the odd-panel one.\r
\r
  - Add a function that returns a bridge from a DT node, reducing the amount of\r
    churn in each and every driver and making it a real incentive to not care\r
    about panels in display drivers but only bridges.\r
\r
  - Add an attach and detach hook into the panel operations, and make it called\r
    automatically by the DRM panel bridge.\r
\r
  - Convert the VC4 DSI host to this new bridge function, and the RaspberryPi\r
    Panel to the new attach and detach hooks.\r
\r
If the general approach is agreed upon, other drivers will obviously be\r
converted to drm_of_get_next.\r
\r
Let me know what you think,\r
Maxime\r
\r
Maxime Ripard (10):\r
  Revert "drm/vc4: dsi: Only register our component once a DSI device is\r
    attached"\r
  drm/bridge: Add a function to abstract away panels\r
  drm/bridge: Add documentation sections\r
  drm/bridge: Document the probe issue with MIPI-DSI bridges\r
  drm/panel: Create attach and detach callbacks\r
  drm/bridge: panel: Call attach and detach for the panel\r
  drm/vc4: dsi: Switch to drm_of_get_next\r
  drm/panel: raspberrypi-touchscreen: Prevent double-free\r
  drm/panel: raspberrypi-touchscreen: Use the attach hook\r
  drm/panel: raspberrypi-touchscreen: Remove MIPI-DSI driver\r
\r
 Documentation/gpu/drm-kms-helpers.rst         |  12 ++\r
 drivers/gpu/drm/bridge/panel.c                |   4 +\r
 drivers/gpu/drm/drm_bridge.c                  | 134 ++++++++++++++-\r
 drivers/gpu/drm/drm_of.c                      |   3 +\r
 drivers/gpu/drm/drm_panel.c                   |  20 +++\r
 .../drm/panel/panel-raspberrypi-touchscreen.c | 159 +++++++++---------\r
 drivers/gpu/drm/vc4/vc4_drv.c                 |   2 +\r
 drivers/gpu/drm/vc4/vc4_dsi.c                 |  53 +++---\r
 include/drm/drm_bridge.h                      |   2 +\r
 include/drm/drm_panel.h                       |   6 +\r
 10 files changed, 273 insertions(+), 122 deletions(-)\r
\r
-- \r
2.31.1\r
\r

^ permalink raw reply	[flat|nested] 22+ messages in thread

end of thread, other threads:[~2021-08-05 12:19 UTC | newest]

Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-20 13:45 [PATCH 00/10] drm/bridge: Make panel and bridge probe order consistent Maxime Ripard
2021-07-20 13:45 ` [PATCH 01/10] Revert "drm/vc4: dsi: Only register our component once a DSI device is attached" Maxime Ripard
2021-07-20 13:45 ` [PATCH 02/10] drm/bridge: Add a function to abstract away panels Maxime Ripard
2021-07-22  7:49   ` Jagan Teki
2021-07-20 13:45 ` [PATCH 03/10] drm/bridge: Add documentation sections Maxime Ripard
2021-07-20 13:45 ` [PATCH 04/10] drm/bridge: Document the probe issue with MIPI-DSI bridges Maxime Ripard
2021-07-21 12:05   ` Daniel Vetter
2021-07-21 12:06     ` Daniel Vetter
2021-07-26 15:16     ` Maxime Ripard
2021-07-27  9:20       ` Daniel Vetter
2021-07-28 13:27         ` Maxime Ripard
2021-07-27  9:42   ` Jagan Teki
2021-07-28 13:35     ` Maxime Ripard
2021-08-05 12:19       ` Jagan Teki
2021-07-20 13:45 ` [PATCH 05/10] drm/panel: Create attach and detach callbacks Maxime Ripard
2021-07-22  7:53   ` Jagan Teki
2021-07-20 13:45 ` [PATCH 06/10] drm/bridge: panel: Call attach and detach for the panel Maxime Ripard
2021-07-20 13:45 ` [PATCH 07/10] drm/vc4: dsi: Switch to drm_of_get_next Maxime Ripard
2021-07-20 13:45 ` [PATCH 08/10] drm/panel: raspberrypi-touchscreen: Prevent double-free Maxime Ripard
     [not found]   ` <YPcFrKLq1dhTcOUL@ravnborg.org>
2021-07-22  9:38     ` Maxime Ripard
2021-07-20 13:45 ` [PATCH 09/10] drm/panel: raspberrypi-touchscreen: Use the attach hook Maxime Ripard
2021-07-20 13:45 ` [PATCH 10/10] drm/panel: raspberrypi-touchscreen: Remove MIPI-DSI driver Maxime Ripard

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).