From: Zhou Zhu <zzhu84@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCHv2 1/4] video: mmp display subsystem
Date: Tue, 04 Sep 2012 02:55:52 +0000 [thread overview]
Message-ID: <CAJATT-6xGeX5jhyRn=XRpZSNuzB6wz09nWK22YSxTOFLhTrX-w@mail.gmail.com> (raw)
In-Reply-To: <1346293222-13692-1-git-send-email-zzhu3@marvell.com>
Hi, Florian,
Would you please help to review my patches?
Also would you please help to apply them if no more issue.
Thank you very much!
On Thu, Aug 30, 2012 at 10:20 AM, Zhou Zhu <zzhu3@marvell.com> wrote:
> Added mmp display subsystem to support Marvell MMP display controllers.
>
> This subsystem contains 4 parts:
> --fb folder
> --core.c
> --hw folder
> --panel folder
>
> 1. fb folder contains implementation of fb.
> fb get path and ovly from common interface and operates on these structures.
>
> 2. core.c provides common interface for a hardware abstraction.
> Major parts of this interface are:
> a) Path: path is a output device connected to a panel or HDMI TV.
> Main operations of the path is set/get timing/output color.
> fb operates output device through path structure.
> b) Ovly: Ovly is a buffer shown on the path.
> Ovly describes frame buffer and its source/destination size, offset, input
> color, buffer address, z-order, and so on.
> Each fb device maps to one ovly.
>
> 3. hw folder contains implementation of hardware operations defined by core.c.
> It registers paths for fb use.
>
> 4. panel folder contains implementation of panels.
> It's connected to path. Panel drivers would also regiester panels and linked
> to path when probe.
>
> Signed-off-by: Zhou Zhu <zzhu3@marvell.com>
> Signed-off-by: Lisa Du <cldu@marvell.com>
--
Thanks,
-Zhou
prev parent reply other threads:[~2012-09-04 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 2:20 [PATCHv2 1/4] video: mmp display subsystem Zhou Zhu
2012-09-01 6:25 ` Laurent Pinchart
2012-09-04 1:50 ` Zhou Zhu
2012-09-04 2:55 ` Zhou Zhu [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='CAJATT-6xGeX5jhyRn=XRpZSNuzB6wz09nWK22YSxTOFLhTrX-w@mail.gmail.com' \
--to=zzhu84@gmail.com \
--cc=linux-fbdev@vger.kernel.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).