Date:   Mon, 25 Apr 2022 20:35:26 -0700
From:   Abhinav Kumar <quic_abhinavk@...cinc.com>
To:     Doug Anderson <dianders@...omium.org>
CC:     Sean Paul <sean@...rly.run>,
        Sankeerth Billakanti <quic_sbillaka@...cinc.com>,
        David Airlie <airlied@...ux.ie>,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        Kuogee Hsieh <quic_khsieh@...cinc.com>,
        LKML <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Stephen Boyd <swboyd@...omium.org>,
        Vinod Koul <vkoul@...nel.org>, Andy Gross <agross@...nel.org>,
        Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
        "Aravind Venkateswaran (QUIC)" <quic_aravindh@...cinc.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        freedreno <freedreno@...ts.freedesktop.org>
Subject: Re: [Freedreno] [PATCH] drm/msm/dp: move add fail safe mode to
 dp_connector_get_mode()



On 4/25/2022 7:18 PM, Doug Anderson wrote:
> Hi,
> 
> On Mon, Apr 25, 2022 at 6:42 PM Abhinav Kumar <quic_abhinavk@...cinc.com> wrote:
>>
>>>> 2) When there was a valid EDID but no 640x480 mode
>>>>
>>>> This is the equipment specific case and the one even I was a bit
>>>> surprised. There is a DP compliance equipment we have in-house and while
>>>> validation, it was found that in its list of modes , it did not have any
>>>> modes which chromebook supported ( due to 2 lanes ). But my
>>>> understanding was that, all sinks should have atleast 640x480 but
>>>> apparently this one did not have that. So to handle this DP compliance
>>>> equipment behavior, we had to do this.
>>>
>>> That doesn't seem right. If there's a valid EDID and the valid EDID
>>> doesn't contain 640x480, are you _sure_ you're supposed to be adding
>>> 640x480? That doesn't sound right to me. I've got a tiny display in
>>> front of me for testing that only has one mode:
>>>
>>>     #0 800x480 65.68 800 840 888 928 480 493 496 525 32000
>>>
>>
>> As I had wrote, DRM core kicks in only when the count of modes is 0.
>> Here what is happening is the count was not 0 but 640x480 was not
>> present in the EDID. So we had to add it explicitly.
>>
>> Your tiny display is a display port display?
>>
>> I am referring to only display port monitors. If your tiny display is
>> DP, it should have had 640x480 in its list of modes.
> 
> My tiny display is actually a HDMI display hooked up to a HDMI to DP
> (active) adapter.
> 
> ...but this is a legal and common thing to have. I suppose possibly my
> HDMI display is "illegal"?
> 
> OK, so reading through the spec more carefully, I do see that the DP
> spec makes numerous mentions of the fact that DP sinks _must_ support
> 640x480. Even going back to DP 1.4, I see section "5.2.1.2 Video
> Timing Format" says that we must support 640x480. It seems like that's
> _intended_ to be used only if the EDID read fails, though or if we
> somehow have to output video without knowledge of the EDID. It seems
> hard to believe that there's a great reason to assume a display will
> support 640x480 if we have more accurate knowledge.
> 
> In any case, I guess I would still say that adding this mode belongs
> in the DRM core. The core should notice that it's a DP connection
> (bridge->type == DRM_MODE_CONNECTOR_DisplayPort) and that 640x480 was
> left out and it should add it. We should also make sure it's not
> "preferred" and is last in the list so we never accidentally pick it.
> If DP truly says that we should always give the user 640x480 then
> that's true for everyone, not just Qualcomm. We should add it in the
> core. If, later, someone wants to hide this from the UI it would be
> much easier if they only needed to modify one place.
> 

So I debugged with kuogee just now using the DP compliance equipment.
It turns out, the issue is not that 640x480 mode is not present.

The issue is that it is not marked as preferred.

Hence we missed this part during debugging this equipment failure.

We still have to figure out the best way to either mark 640x480 as 
preferred or eliminate other modes during the test-case so that 640x480 
is actually picked by usermode.

Now that being said, the fix still doesn't belong in the framework. It 
has to be in the msm/dp code.

Different vendors handle this failure case differently looks like.

Lets take below snippet from i915 as example.

3361 	if (intel_connector->detect_edid == NULL ||
3362 	    connector->edid_corrupt ||
3363 	    intel_dp->aux.i2c_defer_count > 6) {
3364 		/* Check EDID read for NACKs, DEFERs and corruption
3365 		 * (DP CTS 1.2 Core r1.1)
3366 		 *    4.2.2.4 : Failed EDID read, I2C_NAK
3367 		 *    4.2.2.5 : Failed EDID read, I2C_DEFER
3368 		 *    4.2.2.6 : EDID corruption detected
3369 		 * Use failsafe mode for all cases
3370 		 */
3371 		if (intel_dp->aux.i2c_nack_count > 0 ||
3372 			intel_dp->aux.i2c_defer_count > 0)
3373 			drm_dbg_kms(&i915->drm,
3374 				    "EDID read had %d NACKs, %d DEFERs\n",
3375 				    intel_dp->aux.i2c_nack_count,
3376 				    intel_dp->aux.i2c_defer_count);
3377 		intel_dp->compliance.test_data.edid = INTEL_DP_RESOLUTION_FAILSAFE;

This marks the fail safe mode and IGT test case reads this to set this 
mode and hence the test passes.

We rely on the chromeOS usermode to output pixel data for this test-case 
and not IGT. We use IGT only for video pattern CTS today but this is a 
different test-case which is failing.

ChromeOS usermode will not pick 640x480 unless we mark it as preferred 
or other modes are eliminated.

So we have to come up with the right way for the usermode to pick 640x480.

We will discuss this a bit more and come up with a different change.

> 
>>> So IMO we _shouldn't_ land ${SUBJECT} patch.
>>>
>>> Just for testing, I also tried a hack to make EDID reading fail
>>> (return -EIO in the MSM dp_aux_transfer() function if msg->request <
>>> 8). Before ${SUBJECT} patch I'd see these modes:
>>>
>>>     #0 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000
>>>     #1 800x600 60.32 800 840 968 1056 600 601 605 628 40000
>>>     #2 800x600 56.25 800 824 896 1024 600 601 603 625 36000
>>>     #3 848x480 60.00 848 864 976 1088 480 486 494 517 33750
>>>     #4 640x480 59.94 640 656 752 800 480 490 492 525 25175
>>>
>>> ...and after ${SUBJECT} patch I'd see:
>>>
>>>     #0 640x480 59.94 640 656 752 800 480 490 492 525 25175
>>>     #1 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000
>>>     #2 800x600 60.32 800 840 968 1056 600 601 605 628 40000
>>>     #3 800x600 56.25 800 824 896 1024 600 601 603 625 36000
>>>     #4 848x480 60.00 848 864 976 1088 480 486 494 517 33750
>>>
>>> ...so your patch causes 640x480 to be prioritized. That also doesn't
>>> seem ideal. If it was ideal, the DRM core should have listed 640x480
>>> first.
>>
>> So this is a different display or these modes are coming due to the
>> drm_add_modes_noedid() call because of the EDID read fail right?
> 
> Right, it's from the !edid case.
> 
> -Doug

Powered by blists - more mailing lists