linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Grazvydas Ignotas <notasas@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH 00/17] OMAP DSS2 model restructuring
Date: Mon, 15 Feb 2010 07:45:24 +0000	[thread overview]
Message-ID: <1266219924.2433.353.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <6ed0b2681002130734k77de274fx5ceb169e0853b58d@mail.gmail.com>

On Sat, 2010-02-13 at 16:34 +0100, ext Grazvydas Ignotas wrote:
> On Mon, Feb 8, 2010 at 5:57 PM, Tomi Valkeinen <tomi.valkeinen@nokia.com> wrote:
> > Here are a bunch of patches that change the DSS2 driver's driver model a bit.
> > This change was triggered by trying to support new hardware, and realizing that
> > the current model just won't work.
> >
> > Currently the omapdss driver is in control of most aspects of the DSS, and
> > omapdss calls necessary functions in display drivers. I made it that way to
> > keep the display drivers simple, and I, naively, thought that it will work
> > because the display panels are using standard bus interfaces and thus will be
> > very similar. I was so wrong =).
> >
> > This patch set moves the control to the display driver. The display driver then
> > calls omapdss functions to perform whatever deed is needed at that time. This
> > will make display drivers slightly more complex, but it will be easier to
> > control the hardware properly with strange or complex display devices.
> >
> > As a simple example, let's look at the update function.
> >
> > Currently user space app issues OMAPFB_UPDATE_WINDOW ioctl, and omapfb driver
> > then calls update() in corresponding dss device struct, which goes to omapdss.
> > omapdss will configure the update, calling the panel driver if needed.
> >
> > After these patches, omapfb will call update() in the panel driver. The panel
> > driver will then call functions in omapdss to setup the update, start the
> > update, and the panel driver will eventually get a callback informing that the
> > update is done.
> >
> > These patches are still under work, but my basic tests on 3430SDP board seems
> > to work ok.
> >
> > The patches can also be found from
> > http://gitorious.org/linux-omap-dss2/linux work branch
> 
> Tested those along with the other series, seems to work fine on
> pandora too. Panel callbacks like set_mirror
> also work now, thanks.
> 
> Tested-by: Grazvydas Ignotas <notasas@gmail.com>

Ok, thanks!

 Tomi



      reply	other threads:[~2010-02-15  7:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 15:57 [PATCH 00/17] OMAP DSS2 model restructuring Tomi Valkeinen
2010-02-08 15:57 ` [PATCH 01/17] OMAP: DSS2: DSI: change DSI bus_lock to semaphore Tomi Valkeinen
2010-02-08 15:57   ` [PATCH 02/17] OMAP: DSS2: DSI: remove auto-update perf measurement Tomi Valkeinen
2010-02-08 15:57     ` [PATCH 03/17] OMAP: DSS2: move run_test() Tomi Valkeinen
2010-02-08 15:57       ` [PATCH 04/17] OMAP: DSS2: move memory_read() Tomi Valkeinen
2010-02-08 15:57         ` [PATCH 05/17] OMAP: DSS2: move set/get_mirror() Tomi Valkeinen
2010-02-08 15:57           ` [PATCH 06/17] OMAP: DSS2: move get/set_rotate() Tomi Valkeinen
2010-02-08 15:57             ` [PATCH 07/17] OMAP: DSS2: move wait_vsync() Tomi Valkeinen
2010-02-08 15:57               ` [PATCH 08/17] OMAP: DSS2: move enable/disable_channel to overlay manager Tomi Valkeinen
2010-02-08 15:57                 ` [PATCH 09/17] OMAP: DSS2: move get_resolution() Tomi Valkeinen
2010-02-08 15:57                   ` [PATCH 10/17] OMAP: DSS2: move get_recommended_bpp() Tomi Valkeinen
2010-02-08 15:57                     ` [PATCH 11/17] OMAP: DSS2: move enable/get_te() Tomi Valkeinen
2010-02-08 15:57                       ` [PATCH 12/17] OMAP: DSS2: move set/get_update_mode() Tomi Valkeinen
2010-02-08 15:57                         ` [PATCH 13/17] OMAP: DSS2: move update() and sync() Tomi Valkeinen
2010-02-08 15:57                           ` [PATCH 14/17] OMAP: DSS2: move enable/disable/suspend/resume Tomi Valkeinen
2010-02-08 15:57                             ` [PATCH 15/17] OMAP: DSS2: move set/get_wss() Tomi Valkeinen
2010-02-08 15:57                               ` [PATCH 16/17] OMAP: DSS2: move timing functions Tomi Valkeinen
2010-02-08 15:57                                 ` [PATCH 17/17] OMAP: DSS2: DSI: Add VC support for update Tomi Valkeinen
2010-02-09 10:15                             ` [PATCH 14/17] OMAP: DSS2: move enable/disable/suspend/resume Grazvydas Ignotas
2010-02-09 12:12                               ` Tomi Valkeinen
2010-02-13 15:34 ` [PATCH 00/17] OMAP DSS2 model restructuring Grazvydas Ignotas
2010-02-15  7:45   ` 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=1266219924.2433.353.camel@tubuntu.research.nokia.com \
    --to=tomi.valkeinen@nokia.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=notasas@gmail.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).