mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Aradhya Bhatia <a-bhatia1@ti.com>,
	dri-devel@lists.freedesktop.org, Marek Vasut <marex@denx.de>,
	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>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case
Date: Fri, 11 Oct 2024 15:02:56 +0300	[thread overview]
Message-ID: <1ea19ca9-25fd-42c3-b495-5df0ab6c3ea3@ideasonboard.com> (raw)
In-Reply-To: <lxcxo3y7z6emrpvisibj6ccr6qx5nozchuyy5aizfvkvvlp44m@jecj6k5y6z2t>

Hi,

On 23/09/2024 15:25, Dmitry Baryshkov wrote:

>> As Dmitry asked me during Plumbers to revalidate if our setup still
>> needs patch 2, I just did that over 6.11.0-next-20240923 (where patch 1
>> is now included). No surprise, it is still needed for our iot2050 device
>> series, otherwise the display remains black.
> 
> Granted that nobody with the DRM_BRIDGE_ATTACH_NO_CONNECTOR + DSI-DP
> spoke in the last several months, I think we'd better merge the patch as
> it is now. If noone objects (last call), I'll do that in one or two
> days.

No one has objected, are we ready to merge?

  Tomi


  reply	other threads:[~2024-10-11 12:03 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
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 [this message]
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=1ea19ca9-25fd-42c3-b495-5df0ab6c3ea3@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --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=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=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®