From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Michael Büsch" <m@bues.ch>
Cc: lo-ml <linux-omap@vger.kernel.org>, Tony Lindgren <tony@atomide.com>
Subject: Re: N8x0 display support (was: Re: The old omapfb support)
Date: Sat, 30 Apr 2011 09:01:03 +0300 [thread overview]
Message-ID: <1304143263.2080.5.camel@deskari> (raw)
In-Reply-To: <1304111048.30575.12.camel@maggie>
On Fri, 2011-04-29 at 23:04 +0200, Michael Büsch wrote:
> On Fri, 2011-04-29 at 16:33 +0300, Tomi Valkeinen wrote:
> > So, my question is: what are the uses of N800's display with the
> > mainline kernel? Are we happy with just having basic display
> > functionality, or do people need all the features in the older blizzard
> > driver?
>
> Well, not sure.
> The OpenWRT project runs an X server on the n810.
> It does so by using the X.org "omapfb" driver module, which
> accesses the hardware through /dev/fb0.
> http://git.pingu.fi/xf86-video-omapfb/
A quick grep shows that there's some manual update support in that tree.
However, all the OMAPFB_UPDATE_WINDOW calls are in omapfb-xv-blizzard.c,
and to me it looks like manual-update is used when Xv is being used, and
auto-update otherwise. So that probably needs some work, either in the
driver or in X.
Perhaps I'll see if I can add deferred IO support to omapfb driver,
which would be turned on when a manual-update display is set to
auto-update mode. That's not exactly the same as auto update, but I
guess it should work for almost all the cases.
While I don't like having auto-update for manual-update displays, I
guess it's still good to have for testing and prototyping purposes.
> So we basically need that to work in one way or another.
> Another thing that we require is turning off the display for
> power saving reasons. We currently do this through
> FBIOBLANK ioctl with parameters FB_BLANK_POWERDOWN/FB_BLANK_UNBLANK.
> (The backlight is turned off by other means with the device asic)
Blanking works with FBIOBLANK. It also turns off the backlight. The
backlight brightness can be controlled
via /sys/class/backlight/display0/
Tomi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-04-30 6:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 12:20 The old omapfb support Tomi Valkeinen
2011-04-19 12:30 ` Tony Lindgren
2011-04-19 12:34 ` Michael Büsch
2011-04-19 12:41 ` Tomi Valkeinen
2011-04-19 12:45 ` Michael Büsch
2011-04-20 8:06 ` Tomi Valkeinen
2011-04-20 11:18 ` Michael Büsch
2011-04-20 11:31 ` Tomi Valkeinen
2011-04-20 11:35 ` Michael Büsch
2011-04-29 13:33 ` N8x0 display support (was: Re: The old omapfb support) Tomi Valkeinen
2011-04-29 14:08 ` Jarkko Nikula
2011-04-29 21:04 ` Michael Büsch
2011-04-29 21:05 ` Michael Büsch
2011-04-30 6:01 ` Tomi Valkeinen [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=1304143263.2080.5.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=m@bues.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.