From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Doug Anderson <dianders@chromium.org>,
Qiqi Zhang <eddy.zhang@rock-chips.com>
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com, airlied@gmail.com,
daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/bridge: ti-sn65dsi86: Fix output polarity setting bug
Date: Tue, 29 Nov 2022 13:45:58 +0200 [thread overview]
Message-ID: <34c2e9c8-9e3d-129c-8295-18ff440f1f84@ideasonboard.com> (raw)
In-Reply-To: <CAD=FV=XAU8qQ1tFV9_4FF9Rd7ouT5ORzt6JUnQ4KqJgRsEXqHw@mail.gmail.com>
On 29/11/2022 03:13, Doug Anderson wrote:
> Hi,
>
> On Fri, Nov 25, 2022 at 2:54 AM Qiqi Zhang <eddy.zhang@rock-chips.com> wrote:
>>
>> According to the description in ti-sn65dsi86's datasheet:
>>
>> CHA_HSYNC_POLARITY:
>> 0 = Active High Pulse. Synchronization signal is high for the sync
>> pulse width. (default)
>> 1 = Active Low Pulse. Synchronization signal is low for the sync
>> pulse width.
>>
>> CHA_VSYNC_POLARITY:
>> 0 = Active High Pulse. Synchronization signal is high for the sync
>> pulse width. (Default)
>> 1 = Active Low Pulse. Synchronization signal is low for the sync
>> pulse width.
>>
>> We should only set these bits when the polarity is negative.
>> Signed-off-by: Qiqi Zhang <eddy.zhang@rock-chips.com>
>> ---
>> drivers/gpu/drm/bridge/ti-sn65dsi86.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi86.c b/drivers/gpu/drm/bridge/ti-sn65dsi86.c
>> index 3c3561942eb6..eb24322df721 100644
>> --- a/drivers/gpu/drm/bridge/ti-sn65dsi86.c
>> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi86.c
>> @@ -931,9 +931,9 @@ static void ti_sn_bridge_set_video_timings(struct ti_sn65dsi86 *pdata)
>> &pdata->bridge.encoder->crtc->state->adjusted_mode;
>> u8 hsync_polarity = 0, vsync_polarity = 0;
>>
>> - if (mode->flags & DRM_MODE_FLAG_PHSYNC)
>> + if (mode->flags & DRM_MODE_FLAG_NHSYNC)
>> hsync_polarity = CHA_HSYNC_POLARITY;
>> - if (mode->flags & DRM_MODE_FLAG_PVSYNC)
>> + if (mode->flags & DRM_MODE_FLAG_NVSYNC)
>> vsync_polarity = CHA_VSYNC_POLARITY;
>
> Looks right to me.
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
>
> I've never seen the polarity matter for any eDP panels I've worked
> with, which presumably explains why this was wrong for so long. As far
Afaik, DP doesn't have sync polarity as such (neither does DSI), and the
sync polarity is just "metadata". So if you're in full-DP domain, I
don't see why it would matter. I guess it becomes relevant when you
convert from DP to some other bus format.
> as I can tell, it's been wrong since the start. Probably you should
> have:
>
> Fixes: a095f15c00e2 ("drm/bridge: add support for sn65dsi86 bridge driver")
>
> I put this on a sc7180-trogdor-lazor device and it didn't make
> anything worse. Since the sync polarity never mattered to begin with,
> I guess this isn't a surprise. ...so I guess that's a weak tested-by:
>
> Tested-by: Douglas Anderson <dianders@chromium.org>
>
> I'm happy to land this patch, but sounds like we're hoping to get
> extra testing so I'll hold off for now.
Looks fine to me and works for me with my DP monitor.
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Tomi
next prev parent reply other threads:[~2022-11-29 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 10:45 Qiqi Zhang
2022-11-28 7:43 ` Laurent Pinchart
2022-11-29 1:13 ` Doug Anderson
2022-11-29 11:45 ` Tomi Valkeinen [this message]
2022-11-30 5:45 ` Qiqi Zhang
2022-11-30 14:58 ` Doug Anderson
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=34c2e9c8-9e3d-129c-8295-18ff440f1f84@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eddy.zhang@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robert.foss@linaro.org \
/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®