linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christian.gmeiner@gmail.com (Christian Gmeiner)
To: linux-arm-kernel@lists.infradead.org
Subject: imx-drm: screen flickering
Date: Tue, 28 Jan 2014 09:29:17 +0100	[thread overview]
Message-ID: <CAH9NwWfjsGbLiuY_cDOrUUQFpeSumVVkr-kV2BRAKtsRgGaYGw@mail.gmail.com> (raw)
In-Reply-To: <CAH9NwWe673znThNPWRvOCyAU2o7M-oouHD7+1tyRcmWTeJ8YFw@mail.gmail.com>

2014-01-28 Christian Gmeiner <christian.gmeiner@gmail.com>:
> Hi all.
>
> From time to time it happens that my LVDS display is flickering (look
> at scroll bar in the video).
> https://drive.google.com/file/d/0B_fznDimUHVubWtvVFlMTkdBbUU/edit?usp=sharing
>
> I really want to find the root cause of it, but I do not know where to
> start. I can trigger this
> sometimes after xscreensever "blanks" the screen and the screensafer
> gets disabled
> via user input.
>
> Any hints?

I forgot to add some details. I am using a 3.12.4 kernel with some a
some patches (dts, ..). As root filesystem
I am using debian 7 and this is how my xorg.conf looks like:

root at OT:/sys/kernel/debug# cat /etc/X11/xorg.conf
#
# DO NOT TOUCH - AUTOGENERATED FILE
#

Section "Device"
        Identifier      "Card0"
        Driver          "modesetting"

EndSection

Section "InputClass"
        Identifier      "keyboard layout"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver          "evdev"
        Option          "XkbLayout" "us"
EndSection


xscreensaver makes use of DPMS. So I think that the the problem could
be related to DPMS somehow.

greets
--
Christian Gmeiner, MSc

  reply	other threads:[~2014-01-28  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  8:11 imx-drm: screen flickering Christian Gmeiner
2014-01-28  8:29 ` Christian Gmeiner [this message]
2014-01-28  8:32   ` Christian Gmeiner
2014-01-29 11:15 ` Sascha Hauer
2014-01-29 14:53   ` Marek Vasut
2014-01-29 16:32     ` Russell King - ARM Linux
2014-01-30  7:45     ` Sascha Hauer
2014-02-01 22:56       ` Marek Vasut
2014-03-24 14:53         ` Christian Gmeiner

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=CAH9NwWfjsGbLiuY_cDOrUUQFpeSumVVkr-kV2BRAKtsRgGaYGw@mail.gmail.com \
    --to=christian.gmeiner@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).