Ping..
At 2025-04-22 15:59:27, "Andy Yan" wrote:
>
>Hi all,
>
>At 2025-03-21 17:48:04, "Maxime Ripard" wrote:
>>On Fri, Mar 21, 2025 at 04:53:38PM +0800, Andy Yan wrote:
>>> From: Andy Yan
>>>
>>> In some application scenarios, we hope to get the corresponding
>>> connector when the brid
Hi all,
At 2025-03-21 17:48:04, "Maxime Ripard" wrote:
>On Fri, Mar 21, 2025 at 04:53:38PM +0800, Andy Yan wrote:
>> From: Andy Yan
>>
>> In some application scenarios, we hope to get the corresponding
>> connector when the bridge's detect hook is invoked.
>>
>> In most cases, we can get the
Hi Maxime,
At 2025-03-21 17:48:04, "Maxime Ripard" wrote:
>On Fri, Mar 21, 2025 at 04:53:38PM +0800, Andy Yan wrote:
>> From: Andy Yan
>>
>> In some application scenarios, we hope to get the corresponding
>> connector when the bridge's detect hook is invoked.
>>
>> In most cases, we can get t
From: Andy Yan
In some application scenarios, we hope to get the corresponding
connector when the bridge's detect hook is invoked.
In most cases, we can get the connector by drm_atomic_get_connector_for_encoder
if the encoder attached to the bridge is enabled, however there will
still be some sc
On Fri, Mar 21, 2025 at 04:53:38PM +0800, Andy Yan wrote:
> From: Andy Yan
>
> In some application scenarios, we hope to get the corresponding
> connector when the bridge's detect hook is invoked.
>
> In most cases, we can get the connector by
> drm_atomic_get_connector_for_encoder
> if the enc