From: Andrzej Hajda <a.hajda@samsung.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: drm/exynos: fimd: vrefresh is zero
Date: Thu, 05 May 2016 11:22:41 +0200 [thread overview]
Message-ID: <572B10E1.4060704@samsung.com> (raw)
In-Reply-To: <572B0E7C.6010408@samsung.com>
On 05/05/2016 11:12 AM, Andrzej Hajda wrote:
>
> Regarding the initial question, mode->vrefresh is set in
> drm_helper_probe_single_connector_modes. I guess division by zero could
> be caused by lack of clock in timings provided by dts timing node.
> As I remember in the past dts timings were passed without provided
> clock, in such case driver calculated mode->clock for some default value
> of vrefresh (60Hz for fimd if I remember correctly). Later validation
> code was added and the clock should be always provided.
> DTS files were updated after some time and the recalculation code was
> removed from fimd driver. So it is possible you are a victim of this change.
One more thing, I have looked at Exynos DTS files in mainline. In case
of exynos5*.dts files clock-frequency is set to 50000, it is of course
insanely low value and vrefresh calculated for such timings will be 0.
So please verify if clock-frequency is not too low in your case.
Regards
Andrzej
>
> Regarding usage by drivers, from a quick look it seems to be used for
> something more than debugging by:
> - amdgpu,
> - exynos,
> - adv7511,
> - intel_dp(?),
> - mdp5_cmd_encoder(?),
> - nouveau,
> - omap(?),
> - tilcdc.
>
> Regards
> Andrzej
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
next prev parent reply other threads:[~2016-05-05 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 21:37 drm/exynos: fimd: vrefresh is zero Tobias Jakobi
2016-05-02 14:22 ` Alex Deucher
2016-05-02 14:30 ` Tobias Jakobi
2016-05-02 20:22 ` Daniel Vetter
2016-05-02 20:30 ` Tobias Jakobi
2016-05-02 21:00 ` Daniel Vetter
2016-05-05 9:12 ` Andrzej Hajda
2016-05-05 9:22 ` Andrzej Hajda [this message]
2016-05-05 16:23 ` Tobias Jakobi
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=572B10E1.4060704@samsung.com \
--to=a.hajda@samsung.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tjakobi@math.uni-bielefeld.de \
/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