From: Pavel Machek <pavel@ucw.cz>
To: tomi.valkeinen@ti.com, linux-fbdev@vger.kernel.org,
linux-omap@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: ivo.g.dimitrov.75@gmail.com, khilman@kernel.org,
tony@atomide.com, aaro.koskinen@iki.fi,
"kernel list" <linux-kernel@vger.kernel.org>,
sre@kernel.org, martijn@brixit.nl,
"Filip Matijević" <filip.matijevic.pz@gmail.com>,
abcloriens@gmail.com, sakari.ailus@linux.intel.com,
pali.rohar@gmail.com, clayton@craftyguy.net,
patrikbachan@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
serge@hallyn.com
Subject: Re: setterm -blank force no longer works after switch to omapdrm
Date: Mon, 19 Feb 2018 20:35:19 +0000 [thread overview]
Message-ID: <20180219203519.GA4936@amd> (raw)
In-Reply-To: <20180219191623.GA2347@amd>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On Mon 2018-02-19 20:16:23, Pavel Machek wrote:
> On Sat 2018-02-17 22:19:27, Pavel Machek wrote:
> > Hi!
> >
> > I used to have use omap fb driver, and blanking worked as expected. It
> > no longer works with omap drm driver. (Tested on v4.16-rc1, but I
> > believe it is broken in older versions, too.)
> >
> > Can you test it on your hw? Any ideas what could be wrong?
> >
> > xset dpms force on/off works as expected.
>
> next-20180219 seems to work as expected, too.
...because I did not switch to omap drm driver for my next- kernels,
yet. Oops :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-02-19 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 21:19 setterm -blank force no longer works after switch to omapdrm Pavel Machek
[not found] ` <20180219191623.GA2347@amd>
2018-02-19 20:35 ` Pavel Machek [this message]
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=20180219203519.GA4936@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=clayton@craftyguy.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=filip.matijevic.pz@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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 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).