From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hai Li" Subject: RE: drm/msm/dsi: hs_zero timing Date: Tue, 1 Sep 2015 11:59:46 -0400 Message-ID: <000601d0e4cf$3adfc0d0$b09f4270$@codeaurora.org> References: <3892D88DBE322D4FA4B7FE095FDA445A07C27BD1AD3D@seldmbx01.corpusers.net> <005401d0dc4b$6591db60$30b59220$@codeaurora.org> <3892D88DBE322D4FA4B7FE095FDA445A07C27BD1AD49@seldmbx01.corpusers.net> <03e301d0de79$b8975940$29c60bc0$@codeaurora.org> <001e01d0e014$b459dbe0$1d0d93a0$@codeaurora.org> <55DFF7F7.3010304@codeaurora.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0414242026==" Return-path: Received: from smtp.codeaurora.org (smtp.codeaurora.org [198.145.29.96]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0F7B77200F for ; Tue, 1 Sep 2015 08:59:49 -0700 (PDT) In-Reply-To: Content-Language: en-us List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: 'Werner Johansson' , 'Archit Taneja' Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org This is a multipart message in MIME format. --===============0414242026== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01D0E4AD.B3CEBD10" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0007_01D0E4AD.B3CEBD10 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Werner, =20 Based on the discussion with our hw team, changing the LNn_CFG4 to all 0 = is the solution for this issue. I will prepare a change to this. =20 Thanks, Hai =20 From: dri-devel [mailto:dri-devel-bounces@lists.freedesktop.org] On = Behalf Of Werner Johansson Sent: Friday, August 28, 2015 2:10 AM To: Archit Taneja Cc: dri-devel@lists.freedesktop.org Subject: Re: drm/msm/dsi: hs_zero timing =20 On Aug 27, 2015 10:56 PM, "Archit Taneja" > wrote: > > There are certain modes (generally for HDMI/DVI) where the refresh = rate > isn't an integer. It can be something like 59.94 Hz, or 60.04Hz. The > above calculation may not work well with such modes. > [...]=20 > We have platforms where the DSI output is connected to HDMI bridge > chips. So the issue I mentioned holds true for msm/dsi too. That makes sense, the non-integer vrefresh rates completely slipped my = mind. Thanks! /wj ------=_NextPart_000_0007_01D0E4AD.B3CEBD10 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi Werner,

 

Based on the discussion with our hw team, changing the LNn_CFG4 to all = 0 is the solution for this issue.

I will prepare a change to this.

 

Thanks,

Hai

 

From:<= /b> = dri-devel [mailto:dri-devel-bounces@lists.freedesktop.org] On Behalf = Of Werner Johansson
Sent: Friday, August 28, 2015 2:10 = AM
To: Archit Taneja
Cc: = dri-devel@lists.freedesktop.org
Subject: Re: drm/msm/dsi: = hs_zero timing

 


On Aug 27, 2015 10:56 PM, = "Archit Taneja" <architt@codeaurora.org> = wrote:
>
> There are certain modes (generally for HDMI/DVI) = where the refresh rate
> isn't an integer. It can be something = like 59.94 Hz, or 60.04Hz. The
> above calculation may not work = well with such modes.
>
[...]
> We have platforms where = the DSI output is connected to HDMI bridge
> chips. So the issue I = mentioned holds true for msm/dsi too.

That makes sense, = the non-integer vrefresh rates completely slipped my = mind.

Thanks!

/wj

<= /body> ------=_NextPart_000_0007_01D0E4AD.B3CEBD10-- --===============0414242026== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0414242026==--