From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Chandrabhanu Mahapatra <cmahapatra@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH V2 0/2] OMAPDSS: DISPC: Peformance improvement of DISPC
Date: Tue, 20 Dec 2011 08:36:09 +0000 [thread overview]
Message-ID: <1324370169.2042.2.camel@deskari> (raw)
In-Reply-To: <1324283602-6383-1-git-send-email-cmahapatra@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Mon, 2011-12-19 at 14:03 +0530, Chandrabhanu Mahapatra wrote:
> Hi everyone,
> the following patch set directs to improve the scaling performance of DISPC
> module which consists of two pacthes.
>
> The first patch is based on code of Lajos Molnar <lajos@ti.com> from Android
> Kernel, which updates the code with new set of coefficients to improve the
> scaling performance.
>
> The second patch is based on some very valuable suggestions by
> Sebastien Fagard <s-fagard@ti.com> and directs to modify the clock
> requirements for scaling to support OMAP4 and avoid clock failure issues.
>
> I have tested these patches on OMAP2, OMAP3 AND OMAP4. To test on 2430SDP
> board I have created a patch to enable the display which will follow later.
>
> All your comments and suggestions are welcome.
Thanks, this looks good. Applied to DSS master branch. There was a minor
conflict with the Makefile, but I fixed that.
Btw, when doing new versions of a patch series, it would be good to have
a short history of the series in the introduction email, so that the
reviewers can easily see what's new in each version.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-20 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 8:45 [PATCH V2 0/2] OMAPDSS: DISPC: Peformance improvement of DISPC Scaling Chandrabhanu Mahapatra
2011-12-20 8:36 ` Tomi Valkeinen [this message]
2011-12-20 12:28 ` Mahapatra, Chandrabhanu
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=1324370169.2042.2.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=cmahapatra@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.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).