dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hai Li" <hali@codeaurora.org>
To: 'Werner Johansson' <werner.johansson@gmail.com>,
	'Archit Taneja' <architt@codeaurora.org>
Cc: dri-devel@lists.freedesktop.org
Subject: RE: drm/msm/dsi: hs_zero timing
Date: Tue, 1 Sep 2015 11:59:46 -0400	[thread overview]
Message-ID: <000601d0e4cf$3adfc0d0$b09f4270$@codeaurora.org> (raw)
In-Reply-To: <CAKVuvfoO6np0Og6w3rx6U7GK+WF4z1dau6bLbsqT2eT1-xXy4w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]

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: 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 <mailto: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


[-- Attachment #1.2: Type: text/html, Size: 4197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-09-01 15:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 18:26 drm/msm/dsi: hs_zero timing Johansson, Werner
2015-08-21 19:55 ` Hai Li
2015-08-21 20:38   ` Johansson, Werner
2015-08-22 13:25     ` Rob Clark
2015-08-24  6:17       ` Werner Johansson
2015-08-24 14:32       ` Hai Li
2015-08-25  1:23         ` Werner Johansson
2015-08-26 15:34           ` Hai Li
2015-08-26 17:39             ` Werner Johansson
2015-08-26 17:46               ` Rob Clark
2015-08-26 18:22                 ` Werner Johansson
2015-08-26 18:31                   ` Rob Clark
2015-08-27  1:42                     ` Werner Johansson
2015-08-28  5:56                       ` Archit Taneja
2015-08-28  6:09                         ` Werner Johansson
2015-09-01 15:59                           ` Hai Li [this message]
2015-09-01 16:27                             ` Werner Johansson
2015-08-28 14:12                         ` hali
2015-08-26 17:49               ` Hai Li
2015-08-26 18:04                 ` Werner Johansson
  -- strict thread matches above, loose matches on Subject: below --
2015-08-21 18:13 Werner Johansson
2015-08-21  1:08 Johansson, Werner

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='000601d0e4cf$3adfc0d0$b09f4270$@codeaurora.org' \
    --to=hali@codeaurora.org \
    --cc=architt@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=werner.johansson@gmail.com \
    /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