mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Devarsh Thakkar <devarsht@ti.com>
To: <andrzej.hajda@intel.com>, <neil.armstrong@linaro.org>,
	<rfoss@kernel.org>
Cc: <praneeth@ti.com>, <vigneshr@ti.com>, <aradhya.bhatia@linux.dev>,
	<s-jain1@ti.com>, <s-wang12@ti.com>, <r-donadkar@ti.com>,
	<h-shenoy@ti.com>, <dmitry.baryshkov@oss.qualcomm.com>,
	<dri-devel@lists.freedesktop.org>, <jani.nikula@intel.com>,
	<simona@ffwll.ch>, <linux-kernel@vger.kernel.org>,
	<airlied@gmail.com>, <maarten.lankhorst@linux.intel.com>,
	<mripard@kernel.org>, <tzimmermann@suse.de>,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH v4] drm/bridge: sii902x: Fix HDMI detection with DRM_BRIDGE_ATTACH_NO_CONNECTOR
Date: Thu, 13 Nov 2025 14:35:52 +0530	[thread overview]
Message-ID: <edff9c4a-c4ba-44b7-86d4-a070ee57d49c@ti.com> (raw)
In-Reply-To: <138857f0-969d-4e99-aafd-d0c4e9aefb66@ideasonboard.com>

Hi Neil, Andrzej, Robert

On 31/10/25 20:40, Tomi Valkeinen wrote:

> Hi,
> 
> On 30/10/2025 17:16, Devarsh Thakkar wrote:
>> The sii902x driver was caching HDMI detection state in a sink_is_hdmi field
>> and checking it in mode_set() to determine whether to set HDMI or DVI
>> output mode. This approach had two problems:
>>
>> 1. With DRM_BRIDGE_ATTACH_NO_CONNECTOR (used by modern display drivers like
>> TIDSS), the bridge's get_modes() is never called. Instead, the
>> drm_bridge_connector helper calls the bridge's edid_read() and updates the
>> connector itself. This meant sink_is_hdmi was never populated, causing the
>> driver to default to DVI mode and breaking HDMI audio.
>>
>> 2. The mode_set() callback doesn't receive atomic state or connector
>> pointer, making it impossible to check connector->display_info.is_hdmi
>> directly at that point.
>>
>> Fix this by moving the HDMI vs DVI decision from mode_set() to
>> atomic_enable(), where we can access the connector via
>> drm_atomic_get_new_connector_for_encoder(). This works for both connector
>> models:
>>
>> - With DRM_BRIDGE_ATTACH_NO_CONNECTOR: Returns the drm_bridge_connector
>>    created by the display driver, which has already been updated by the
>> helper's call to drm_edid_connector_update()
>>
>> - Without DRM_BRIDGE_ATTACH_NO_CONNECTOR (legacy): Returns the connector
>>    embedded in sii902x struct, which gets updated by the bridge's own
>> get_modes()
>>
>> Fixes: 3de47e1309c2 ("drm/bridge: sii902x: use display info is_hdmi")
>> Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
>> ---
>> V4: Shift HDMI detection to atomic_enable() and remove sink_is_hdmi caching
>> V3: Use drm_edid_connector_update without edid NULL check
>> V2: Use drm_edid_connector_update to detect HDMI
>>
<snip>

> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
> 

I wanted to follow up on this patch which fixes HDMI audio for the 
sii902x bridge driver when used with DRM_BRIDGE_ATTACH_NO_CONNECTOR. The 
patch has been reviewed by Tomi Valkeinen and addresses a real bug where 
HDMI audio is broken when using modern display drivers like TIDSS.

Could you please let me know if there are any concerns or if this can
be pulled in ?

Regards
Devarsh

  reply	other threads:[~2025-11-13  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 15:16 Devarsh Thakkar
2025-10-31 15:10 ` Tomi Valkeinen
2025-11-13  9:05   ` Devarsh Thakkar [this message]
2025-11-21 15:03 ` Neil Armstrong

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=edff9c4a-c4ba-44b7-86d4-a070ee57d49c@ti.com \
    --to=devarsht@ti.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=aradhya.bhatia@linux.dev \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=h-shenoy@ti.com \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=praneeth@ti.com \
    --cc=r-donadkar@ti.com \
    --cc=rfoss@kernel.org \
    --cc=s-jain1@ti.com \
    --cc=s-wang12@ti.com \
    --cc=simona@ffwll.ch \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    --cc=vigneshr@ti.com \
    /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®