From: Aradhya Bhatia <a-bhatia1@ti.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Jan Kiszka <jan.kiszka@siemens.com>, Marek Vasut <marex@denx.de>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: 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>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case
Date: Sat, 22 Jun 2024 17:16:58 +0530 [thread overview]
Message-ID: <71e809fa-b471-4bb3-8f7d-e497397c0de4@ti.com> (raw)
In-Reply-To: <o4bwopeuyxm6344oqqm3e7p3xcx76aw2trsiuhhfyhel2e7po7@sz2jaj6i7kqd>
On 17-Jun-24 13:41, Dmitry Baryshkov wrote:
> On Mon, Jun 17, 2024 at 07:40:32AM GMT, Jan Kiszka wrote:
>> On 16.02.24 15:57, Marek Vasut wrote:
>>> On 2/16/24 10:10, Tomi Valkeinen wrote:
>>>> 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 .
Isn't there any way for the second patch to move forward as well though?
The bridge device (under DPI to (e)DP mode) cannot really work without
it, and the patches have been pending idle for a long time. =)
>>
>> My local patches still apply on top of 6.10-rc4, so I don't think this
>> ever happened. What's still holding up this long-pending fix (at least
>> for our devices)?
>
> Neither of the patches contains Fixes tags. If the first patch fixes an
> issue in previous kernels, please consider following the stable process.
>
> If we are unsure about the second patch, please send the first patch
> separately, adding proper tags.
>
Thanks Dmitry! I can send the patches again with the required fixes
tags (or just patch-1 if we cannot do anything about patch-2).
--
Regards
Aradhya
next prev parent reply other threads:[~2024-06-22 11:47 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
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 [this message]
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=71e809fa-b471-4bb3-8f7d-e497397c0de4@ti.com \
--to=a-bhatia1@ti.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--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