From: "Hai Li" <hali@codeaurora.org>
To: 'Werner Johansson' <werner.johansson@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: RE: drm/msm/dsi: hs_zero timing
Date: Wed, 26 Aug 2015 13:49:47 -0400 [thread overview]
Message-ID: <002a01d0e027$9aeb90a0$d0c2b1e0$@codeaurora.org> (raw)
In-Reply-To: <CAKVuvfrEkHAFxgopHVwNoGispT1TY0Rp25Fv+jJ3j8Y+BoCLKA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1435 bytes --]
Thanks Werner to test it out. I will focus on the dphy timing calculation then.
It’s better to avoid discussing the excel formula publicly. :)
Thanks,
Hai
From: Werner Johansson [mailto:werner.johansson@gmail.com]
Sent: Wednesday, August 26, 2015 1:39 PM
To: Hai Li
Cc: Rob Clark; werner.johansson@sonymobile.com; dri-devel@lists.freedesktop.org
Subject: RE: drm/msm/dsi: hs_zero timing
On Aug 26, 2015 08:34, "Hai Li" <hali@codeaurora.org <mailto:hali@codeaurora.org> > wrote:
>
> Hi Werner,
>
> Thanks for sharing this. The DPHY timings in downstream dtsi are exactly the same as the excel calculation, but slightly different from the output of drm code as you posted. (e.g hs_zero is 116 vs 118)
> I think it is caused by some precision loss during driver calculation, but I need to double check.
>
> Could you help to try configuring the same DPHY timings as downstream, but leave the values in DSIPHY_LNx_CFG4 as is, to see if it works?
116 to hs_zero works fine without any other changes (only 118 and every eighth number up and down from there fails with this panel timing), so if we can do something to make sure we hit a working value for hs_zero without touching anything else that would be great!
Thanks for checking the timings and let me know if you want me to test anything else. Is the excel formula considered public so we can discuss it here?
/wj
[-- Attachment #1.2: Type: text/html, Size: 4871 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
next prev parent reply other threads:[~2015-08-26 17:49 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
2015-09-01 16:27 ` Werner Johansson
2015-08-28 14:12 ` hali
2015-08-26 17:49 ` Hai Li [this message]
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='002a01d0e027$9aeb90a0$d0c2b1e0$@codeaurora.org' \
--to=hali@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.