From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Refactor panel fitting on the LVDS.
Date: Sat, 17 Jul 2010 18:15:46 -0700 [thread overview]
Message-ID: <20100717181546.2d52b7b2@jbarnes-x201> (raw)
In-Reply-To: <1279370324-12761-2-git-send-email-chris@chris-wilson.co.uk>
On Sat, 17 Jul 2010 13:38:44 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Move the common routines into separate functions to not only increase
> readability, but also throwaway surplus code.
>
> In doing so, we review the calculation of the aspect preserving
> scaling and avoid the use of fixed-point until we need to calculate
> the accurate scale factor.
>
> 1 files changed, 128 insertions(+), 194 deletions(-)
Nice cleanups, that function was getting too big... misc nitpicks
below.
> + /* keep the border be even */
> + if (border & 1)
> + border++;
May as well fix the comment here or combine it with the above. There
are a few other comments like this elsewhere too.
While you're in there it would also be cool to write a small CRTC mode
verification function that checks the htotal/vtotal/etc against the
constraints documented in the manual (e.g. sync before end, active
divisible by 2 in ganged mode, etc). If you're feeling adventurous
anyway. :)
Other than that:
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-07-18 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 12:38 [PATCH 1/2] drm/i915: Remove the redundant check for a fixed_panel_mode Chris Wilson
2010-07-17 12:38 ` [PATCH 2/2] drm/i915: Refactor panel fitting on the LVDS Chris Wilson
2010-07-17 12:48 ` Chris Wilson
2010-07-18 1:15 ` Jesse Barnes [this message]
2010-07-18 11:07 ` Chris Wilson
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=20100717181546.2d52b7b2@jbarnes-x201 \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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