← Back to team overview

linaro-release team mailing list archive

[Bug 824506] Re: Graphics driver on i.MX53 Android issues

 

In today's meeting, we might want to keep this as is in FSL's kernel. If
the bug is in the user space, we should fix all the bugs in user space.
I'll mark this bug as wishlist in FSL landing team for tracking the
issues.


** Changed in: linaro-landing-team-freescale
   Importance: Undecided => Wishlist

** Changed in: linaro-landing-team-freescale
       Status: Confirmed => Opinion

-- 
You received this bug notification because you are a member of Linaro
Release Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/824506

Title:
  Graphics driver on i.MX53 Android issues

Status in Linaro Android:
  Fix Committed
Status in Linaro Freescale Landing Team Project:
  Opinion

Bug description:
  Booting Android on i.MX53 QSB using your bsp/freescale/linux-linaro-
  android.git kernel, with a display at a resolution with >= 1024 pixels
  width, results in endless loops of

  [...]
  <7>[  120.044524] DMFC high resolution has set, will not change
  <7>[  120.144532] DMFC high resolution has set, will not change
  <7>[  120.224553] DMFC high resolution has set, will not change
  [...]

  This error message comes from drivers/mxc/ipu3/ipu_disp.c,
  _ipu_dmfc_init.

  _ipu_dmfc_init is called from _ipu_dmfc_set_wait4eot, ipu_probe and ipu_resume.
  _ipu_dmfc_set_wait4eot is called by ipu_init_channel_buffer (exported
  through the IPU_INIT_CHANNEL_BUFFER ioctl).

  There doesn't seem to be a reasonable code path that could hit those
  10+ times a second, but I haven't put a lot of time into debugging this
  yet.

  In my current builds, I've speeded it up by hiding the warning and
  avoiding the logging activity. We can now see the right picture, but
  any screen update (e.g. moving the mouse cursor, or automatic updates
  when e.g. running 0xbench) causes the screen to blank for a while (and
  then come back up showing what it should be showing, behaves pretty
  much like an e-ink display). My current guess is that any screen
  update causes the driver to re-initialize, causing both the message
  and the blanking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-android/+bug/824506/+subscriptions