From: Manjunath Hadli <manjunath.hadli@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: [RFC PATCH 0/3] fbdev driver for dm644x
Date: Mon, 26 Sep 2011 13:47:06 +0000 [thread overview]
Message-ID: <1317044109-7429-1-git-send-email-manjunath.hadli@ti.com> (raw)
This patch series adds an fbdev driver for Texas
Instruments Davinci SoC.The display subsystem consists
of OSD and VENC, with OSD supporting 2 RGb planes and
2 video planes.
http://focus.ti.com/general/docs/lit/
getliterature.tsp?literatureNumber=sprue37d&fileType=pdf
A good amount of the OSD and VENC enabling code is
present in the kernel, and this patch series adds the
fbdev interface.
The fbdev driver exports 4 nodes representing each
plane to the user - from fb0 to fb3.
Manjunath Hadli (3):
davinci: vpbe: enable vpbe for fbdev addition
davinci: vpbe: add fbdev driver for dm644x
davinci: vpbe: add build infrastructure for fbdev driver
drivers/media/video/davinci/Kconfig | 13 +
drivers/media/video/davinci/Makefile | 1 +
drivers/media/video/davinci/vpbe_display.c | 6 +
drivers/media/video/davinci/vpbe_fb.c | 2537 +++++++++++++++++++++++++++
drivers/media/video/davinci/vpbe_fb.h | 66 +
drivers/media/video/davinci/vpbe_fb_ioctl.h | 159 ++
drivers/media/video/davinci/vpbe_osd.c | 793 +++++++++-
drivers/media/video/davinci/vpbe_venc.c | 84 +
include/media/davinci/vpbe_osd.h | 64 +-
include/media/davinci/vpbe_venc.h | 21 +
10 files changed, 3735 insertions(+), 9 deletions(-)
create mode 100644 drivers/media/video/davinci/vpbe_fb.c
create mode 100644 drivers/media/video/davinci/vpbe_fb.h
create mode 100644 drivers/media/video/davinci/vpbe_fb_ioctl.h
next reply other threads:[~2011-09-26 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 13:47 Manjunath Hadli [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-19 11:40 [RFC PATCH 0/3] fbdev driver for dm644x Hadli, Manjunath
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=1317044109-7429-1-git-send-email-manjunath.hadli@ti.com \
--to=manjunath.hadli@ti.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