From: Marek Vasut <marex@denx.de>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Aradhya Bhatia <a-bhatia1@ti.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,
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: Fri, 16 Feb 2024 15:57:54 +0100 [thread overview]
Message-ID: <bc96c6b5-a7f8-4ef3-a89b-bf577943f11c@denx.de> (raw)
In-Reply-To: <b2052bc9-b2da-489b-9e5b-3c9b4f6c1c99@ideasonboard.com>
On 2/16/24 10:10, Tomi Valkeinen wrote:
> On 15/02/2024 11:03, Alexander Stein wrote:
>> 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.
>
> Ok. Does anyone have a worry that these patches make the situation worse
> for the DSI case than it was before? Afaics, if the DSI lanes are not
> set up early enough by the DSI host, the driver would break with and
> without these patches.
>
> These do fix the driver for DRM_BRIDGE_ATTACH_NO_CONNECTOR and DPI, so
> I'd like to merge these unless these cause a regression with the DSI case.
1/2 looks good to me, go ahead and apply .
next prev parent reply other threads:[~2024-02-16 14:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 11:27 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
2024-02-16 9:10 ` Tomi Valkeinen
2024-02-16 14:57 ` Marek Vasut [this message]
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=bc96c6b5-a7f8-4ef3-a89b-bf577943f11c@denx.de \
--to=marex@denx.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a-bhatia1@ti.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.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=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
all inboxes | Powered by JetHome®