From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] drm/sun4i: dotclock: Allow divider = 127
Date: Sun, 18 Sep 2016 21:13:47 +0200 [thread overview]
Message-ID: <20160918191347.GH17518@lukather> (raw)
In-Reply-To: <20160915151402.15992-4-wens@csie.org>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
On Thu, Sep 15, 2016 at 11:14:01PM +0800, Chen-Yu Tsai wrote:
> The dot clock divider is 7 bits wide, and the divider range is 1 ~ 127,
> or 6 ~ 127 if phase offsets are used. The 0 register value also
> represents a divider of 1 or bypass.
>
> Make the end condition of the for loop inclusive of 127 in the
> round_rate callback.
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-18 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 15:13 [PATCH 0/4] drm/sun4i: rgb and dotclock misc fixes and improvements Chen-Yu Tsai
2016-09-15 15:13 ` [PATCH 1/4] drm/sun4i: rgb: Declare RGB encoder and connector as MIPI DPI Chen-Yu Tsai
2016-09-18 19:12 ` Maxime Ripard
2016-09-19 15:20 ` Chen-Yu Tsai
2016-09-15 15:14 ` [PATCH 2/4] drm/sun4i: dotclock: Fix clock rate read back calcation Chen-Yu Tsai
2016-09-18 19:14 ` Maxime Ripard
2016-09-15 15:14 ` [PATCH 3/4] drm/sun4i: dotclock: Allow divider = 127 Chen-Yu Tsai
2016-09-18 19:13 ` Maxime Ripard [this message]
2016-09-15 15:14 ` [PATCH 4/4] drm/sun4i: dotclock: Round to closest clock rate Chen-Yu Tsai
2016-09-18 19:16 ` Maxime Ripard
2016-09-19 15:36 ` Chen-Yu Tsai
2016-09-20 7:20 ` Maxime Ripard
2016-09-20 7:19 ` Maxime Ripard
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=20160918191347.GH17518@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).