linaro-release team mailing list archive

[Launchpad Bug Tracker <824506@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug by Fathi Boudra (fboudra):

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.

** Affects: linaro-landing-team-freescale
     Importance: Undecided
     Assignee: Haitao Zhang (minipanda)
         Status: Confirmed

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