linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jjo.braun@gmail.com (Johannes Braun)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale i.MX351: Poor framebuffer performance with 7 inch display
Date: Fri, 12 Jul 2013 10:19:16 +0200	[thread overview]
Message-ID: <CADwvPCsm4UEGLH_mfpeoZ7L-wSTqTgicYXd6+_YuFSxGy57o2Q@mail.gmail.com> (raw)

Dear mailing list,

our current board design is based on a freescale i.MX35 processor.
First some information to the used arm processor. It is an i.MX351 and
its core is clocked to 523Mhz. We have connected a 7 inch display with
a resolution of 800x480 pixels directly to the arm. The display is
working but the performance with qt embedded is very poor. When the
complete display content changes, e.g. from red to green or from blue
to black, there is a bad "wipe effect". The new display content wipes
from the top down to the bottom of the display.

To test the performance without qt embedded I wrote a small c program
which writes a color array directly to the framebuffer device
(/dev/fb0). This program updates the complete framebuffer content
every second. From red to green, from green to blue, from blue to
black and so on. The "wipe effect" is also visible. But less
pronounced than with qt embedded. Shure qt embedded decreases the
performance, but I don`t think this is the core issue for my
performance problems.

There is another point I noticed. The defaut bpp (bit per pixel) value
in the driver is 16. Changing the drivers bpp up to 32 decreases the
performance rapidly. To change the bpp I used the kernel parameter
video=mx3fb:bpp=32.

So I think the core issue is either the performace of the arm itself,
the ram throughput or the driver mx3fb.c. Maybe someone who uses a
similar design could share some information about the performance of
this design. Also I will be gratefull for hints to increase my
performance or to find the bottleneck.

Thanks.


---
Johannes

                 reply	other threads:[~2013-07-12  8:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CADwvPCsm4UEGLH_mfpeoZ7L-wSTqTgicYXd6+_YuFSxGy57o2Q@mail.gmail.com \
    --to=jjo.braun@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).