[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e95984d9-7952-2b0a-4682-2761db51ab53@quicinc.com>
Date: Tue, 22 Feb 2022 16:44:56 -0800
From: Kuogee Hsieh <quic_khsieh@...cinc.com>
To: Stephen Boyd <swboyd@...omium.org>, <agross@...nel.org>,
<airlied@...ux.ie>, <bjorn.andersson@...aro.org>,
<daniel@...ll.ch>, <dmitry.baryshkov@...aro.org>,
<dri-devel@...ts.freedesktop.org>, <robdclark@...il.com>,
<sean@...rly.run>, <vkoul@...nel.org>
CC: <quic_abhinavk@...cinc.com>, <quic_aravindh@...cinc.com>,
<quic_sbillaka@...cinc.com>, <freedreno@...ts.freedesktop.org>,
<linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 1/4] drm/msm/dpu: adjust display_v_end for eDP and DP
On 2/18/2022 6:48 PM, Stephen Boyd wrote:
> Quoting Kuogee Hsieh (2022-02-17 13:36:25)
>> The “DP timing” requires the active region to be defined in the
>> bottom-right corner of the frame dimensions which is different
>> with DSI. Therefore both display_h_end and display_v_end need
>> to be adjusted accordingly. However current implementation has
>> only display_h_end adjusted.
>>
>> Signed-off-by: Kuogee Hsieh <quic_khsieh@...cinc.com>
>> ---
> Is this not a problem for me because this is set already to something
> correct in the hardware?
There will have some pixels step into front porch area.
It should not cause any visual problem.
> Reviewed-by: Stephen Boyd <swboyd@...omium.org>
Powered by blists - more mailing lists