From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Aradhya Bhatia <a-bhatia1@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Sam Ravnborg <sam@ravnborg.org>,
dri-devel@lists.freedesktop.org, marex@denx.de,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case
Date: Thu, 15 Feb 2024 10:03:41 +0100 [thread overview]
Message-ID: <3277848.aeNJFYEL58@steina-w> (raw)
In-Reply-To: <2f3bb86b-6f8c-4807-985e-344a0c47864c@siemens.com>
Hi everyone,
Am Donnerstag, 15. Februar 2024, 09:53:54 CET schrieb Jan Kiszka:
> On 11.12.23 09:07, Aradhya Bhatia wrote:
> > On 06/12/23 17:41, Tomi Valkeinen wrote:
> >> Hi,
> >>
> >> On 08/11/2023 14:45, Alexander Stein wrote:
> >>> Hi Tomi,
> >>>
> >>> Am Mittwoch, 8. November 2023, 12:27:21 CET schrieb Tomi Valkeinen:
> >>>> These two patches are needed to make tc358767 work in the
> >>>> DRM_BRIDGE_ATTACH_NO_CONNECTOR case, at least when using a DP
> >>>> connector.
> >>>>
> >>>> I have tested this with TI AM654 EVM with a tc358767 add-on card
> >>>> connected to a DP monitor.
> >>>
> >>> Just a question regarding the usage of this DSI-DP bridge.
> >>> What is the state of the DSI lanes after the DSI host has been
> >>> initialized,
> >>> but before calling atomic_pre_enable? AFAIK this bridge requires LP-11
> >>> on DSI
> >>> at any time for accessing the AUX channel.
> >
> > + Marek
> >
> > Marek, Alexander,
> >
> > A quick grep tells me that you have added devicetree for tc358767 in DSI
> > to (e)DP mode on other platforms. Could you please test these patches
> > and report if you find any issue?
Sorry, I can't provide any feedback here. I've yet to setup the DSI-DP
correctly.
Best regards,
Alexander
> Is this the last blocker to move forward with these fixes? I'd really
> like to see them finally merged.
>
> Thanks,
> Jan
--
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/
next prev parent reply other threads:[~2024-02-15 9:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 11:27 [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case Tomi Valkeinen
2023-11-08 11:27 ` [PATCH v2 1/2] drm/bridge: tc358767: Add format negotiation hooks for DPI/DSI to (e)DP Tomi Valkeinen
2024-06-17 8:09 ` Dmitry Baryshkov
2024-06-22 12:19 ` Dmitry Baryshkov
2023-11-08 11:27 ` [PATCH v2 2/2] drm/bridge: tc358767: Fix link properties discovery Tomi Valkeinen
2023-11-08 12:45 ` [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case Alexander Stein
2023-11-08 13:06 ` Tomi Valkeinen
2023-12-06 12:11 ` Tomi Valkeinen
2023-12-11 8:07 ` Aradhya Bhatia
2024-02-15 8:53 ` Jan Kiszka
2024-02-15 9:03 ` Alexander Stein [this message]
2024-02-16 9:10 ` Tomi Valkeinen
2024-02-16 14:57 ` Marek Vasut
2024-06-17 5:40 ` Jan Kiszka
2024-06-17 8:11 ` Dmitry Baryshkov
2024-06-22 11:46 ` Aradhya Bhatia
2024-06-22 12:19 ` Dmitry Baryshkov
2024-06-24 9:37 ` Aradhya Bhatia
2024-06-24 9:49 ` Dmitry Baryshkov
2024-06-24 10:07 ` Alexander Stein
2024-06-24 10:17 ` Dmitry Baryshkov
2024-08-26 19:35 ` Jan Kiszka
2024-08-28 13:32 ` Tomi Valkeinen
2024-09-23 7:42 ` Jan Kiszka
2024-09-23 12:25 ` Dmitry Baryshkov
2024-10-11 12:02 ` Tomi Valkeinen
2024-10-12 8:07 ` Dmitry Baryshkov
2023-12-11 8:42 ` Alexander Stein
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=3277848.aeNJFYEL58@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a-bhatia1@ti.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jan.kiszka@siemens.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=sam@ravnborg.org \
--cc=tomi.valkeinen@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox