From: "Ville Syrjälä" <syrjala@sci.fi>
To: Chandrabhanu Mahapatra <cmahapatra@ti.com>
Cc: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] OMAPDSS: DISPC: Enable predecimation
Date: Thu, 15 Mar 2012 22:28:11 +0000 [thread overview]
Message-ID: <20120315222811.GN17132@sci.fi> (raw)
In-Reply-To: <1331812108-9776-1-git-send-email-cmahapatra@ti.com>
On Thu, Mar 15, 2012 at 05:18:28PM +0530, Chandrabhanu Mahapatra wrote:
> In OMAP3 and OMAP4, the DISPC Scaler can downscale an image up to 4 times, and
> up to 2 times in OMAP2. However, with predecimation, the image can be reduced
> to 16 times by fetching only the necessary pixels in memory. Then this
> predecimated image can be downscaled further by the DISPC scaler.
Now, where does that number 16 come from? IIRC the hardware can skip
basically any number of pixels/rows. I certainly didn't add any such
limit to the code in the harmattan kernel, and distinctly remember
being able to downscale the N9/N950 UI even down to 1 pixel size :)
> Based on the downscaling required, a prior calculation of predecimation values
> for width and height of an image is done. Since, Predecimation reduces quality
> of an image higher priorty is given to DISPC Scaler for downscaling.
>
> This code was successfully tested on OMAP2, OMAP3 and OMAP4. Horizontal and
> vertical predecimation worked fine except for some synclost errors due to
> undocumented errata in OMAP3 which are fixed later and skewed images were seen
> on OMAP2 and OMAP3 during horizontal predecimation which will be addressed in
> the future patches.
All the rotation offset calculations still look suspiciously different
to what is in the harmattan kernel. I remember that the original code
was quite broken, and I fixed a lot of things when I was implementing
pre-decimation and some rotation stuff for the N9/N950. Too bad I never
managed to push that stuff upstream...
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <syrjala@sci.fi>
To: Chandrabhanu Mahapatra <cmahapatra@ti.com>
Cc: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] OMAPDSS: DISPC: Enable predecimation
Date: Fri, 16 Mar 2012 00:28:11 +0200 [thread overview]
Message-ID: <20120315222811.GN17132@sci.fi> (raw)
In-Reply-To: <1331812108-9776-1-git-send-email-cmahapatra@ti.com>
On Thu, Mar 15, 2012 at 05:18:28PM +0530, Chandrabhanu Mahapatra wrote:
> In OMAP3 and OMAP4, the DISPC Scaler can downscale an image up to 4 times, and
> up to 2 times in OMAP2. However, with predecimation, the image can be reduced
> to 16 times by fetching only the necessary pixels in memory. Then this
> predecimated image can be downscaled further by the DISPC scaler.
Now, where does that number 16 come from? IIRC the hardware can skip
basically any number of pixels/rows. I certainly didn't add any such
limit to the code in the harmattan kernel, and distinctly remember
being able to downscale the N9/N950 UI even down to 1 pixel size :)
> Based on the downscaling required, a prior calculation of predecimation values
> for width and height of an image is done. Since, Predecimation reduces quality
> of an image higher priorty is given to DISPC Scaler for downscaling.
>
> This code was successfully tested on OMAP2, OMAP3 and OMAP4. Horizontal and
> vertical predecimation worked fine except for some synclost errors due to
> undocumented errata in OMAP3 which are fixed later and skewed images were seen
> on OMAP2 and OMAP3 during horizontal predecimation which will be addressed in
> the future patches.
All the rotation offset calculations still look suspiciously different
to what is in the harmattan kernel. I remember that the original code
was quite broken, and I fixed a lot of things when I was implementing
pre-decimation and some rotation stuff for the N9/N950. Too bad I never
managed to push that stuff upstream...
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-15 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 11:48 [PATCH 1/2] OMAPDSS: DISPC: Enable predecimation Chandrabhanu Mahapatra
2012-03-15 11:49 ` Chandrabhanu Mahapatra
2012-03-15 22:28 ` Ville Syrjälä [this message]
2012-03-15 22:28 ` Ville Syrjälä
2012-03-16 11:59 ` Mahapatra, Chandrabhanu
2012-03-16 12:11 ` 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=20120315222811.GN17132@sci.fi \
--to=syrjala@sci.fi \
--cc=cmahapatra@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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.