All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: dri-devel@lists.freedesktop.org
Subject: RFC: DSI/DRM multiplexer bridge
Date: Wed, 05 Apr 2023 16:09:16 +0200	[thread overview]
Message-ID: <2991779.e9J7NaK4W3@steina-w> (raw)

Hi,

my platform has a DIP switch controlled multiplexer for MIPI DSI output 
signals. One output has a TI SN65DSI84 (LVDS) and the other output has a TI 
SN65DSI86 (eDP) attached to it. The Multiplexer status can be read back from a 
GPIO. The GPIO is also IRQ capable, so it would be possible to support hotplug 
additionally later on.

My initial idea was to create a DRM multiplexer bridge driver which (depending 
on the input GPIO) allows only one output to be enabled. Unfortunately ti-
sn65dsi86.c driver expects a DSI host on remote node 0 (see ti_sn_attach_host 
and ti_sn_bridge_parse_dsi_host), so it does not work. ti-sn65dsi83.c just 
requires a drm_bridge.

What is the best approach for this? I currently see two approaches:
* Create an explicit DSI/DRM multiplexer bridge driver which registers itself 
as DSI host
* Create a DRM multiplexer bridge (only). But this needs to remove the DSI 
device registration from ti-sn65dsi86.c

I am aware that DSI support is suboptimal, so I'm not sure which approach on 
the TI bridge drivers is the correct one and needs to be considered as given.
Any ideas?

Best regards,
Alexander
-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/



             reply	other threads:[~2023-04-05 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 14:09 Alexander Stein [this message]
2023-04-05 14:39 ` RFC: DSI/DRM multiplexer bridge Jagan Teki
2023-04-06  8:33   ` Alexander Stein
2023-04-06  8:37     ` Daniel Vetter
2023-04-06  9:55       ` Jagan Teki
2023-04-11  7:47         ` Alexander Stein
2023-04-12  6:22           ` 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=2991779.e9J7NaK4W3@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=dri-devel@lists.freedesktop.org \
    /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.