mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	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>
Subject: Re: [PATCH 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case
Date: Tue, 19 Dec 2023 12:00:04 +0200	[thread overview]
Message-ID: <77bdddbb-cb1a-4848-9249-72bb7a6cd126@ideasonboard.com> (raw)
In-Reply-To: <0ba64662-b49e-4132-88ea-fcb813af1270@siemens.com>

On 15/12/2023 15:33, Jan Kiszka wrote:
> On 31.10.23 14:26, Tomi Valkeinen wrote:
>> These two patches are needed to make tc358767 work in the
>> DRM_BRIDGE_ATTACH_NO_CONNECTOR case, at least when using a DP connector.
>> The first patch, "drm/bridge: tc358767: Support input format negotiation
>> hook" was already sent separately, but I included it here for
>> completeness, as both are needed to get a working display.
>>
>> I have tested this with TI AM654 EVM with a tc358767 add-on card.
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>> ---
>> Aradhya Bhatia (1):
>>        drm/bridge: tc358767: Support input format negotiation hook
>>
>> Tomi Valkeinen (1):
>>        drm/bridge: tc358767: Fix link properties discovery
>>
>>   drivers/gpu/drm/bridge/tc358767.c | 32 ++++++++++++++++++++++++++++++++
>>   1 file changed, 32 insertions(+)
>> ---
>> base-commit: 79d94360d50fcd487edcfe118a47a2881534923f
>> change-id: 20231031-tc358767-58e3ebdf95f0
>>
>> Best regards,
> 
> What's the plan for these fixes? I'm not yet seeing them in Linus' tree,
> thus also not in stable.
> 
> Jan
> 

The discussion continued in v2 of the series. There are some open 
question in the tc358767 behavior.

  Tomi


      reply	other threads:[~2023-12-19 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 13:26 Tomi Valkeinen
2023-10-31 13:26 ` [PATCH 1/2] drm/bridge: tc358767: Support input format negotiation hook Tomi Valkeinen
2023-10-31 13:26 ` [PATCH 2/2] drm/bridge: tc358767: Fix link properties discovery Tomi Valkeinen
2023-10-31 16:02   ` Aradhya Bhatia
2023-10-31 17:59 ` [PATCH 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case Jan Kiszka
2023-12-15 13:33 ` Jan Kiszka
2023-12-19 10:00   ` Tomi Valkeinen [this message]

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=77bdddbb-cb1a-4848-9249-72bb7a6cd126@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.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=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.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®