From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Davinci fbdev driver and enable it for DMx platform
Date: Wed, 24 Apr 2013 23:02:15 +0200 [thread overview]
Message-ID: <1780031.B4OAypccep@avalon> (raw)
In-Reply-To: <1366804808-22720-1-git-send-email-prabhakar.csengg@gmail.com>
Hi Prabhakar,
Thank you for the patch.
On Wednesday 24 April 2013 17:30:02 Prabhakar Lad wrote:
> From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>
> 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.
The obvious question is: why not a KMS driver instead ? :-)
> Lad, Prabhakar (6):
> media: davinci: vpbe: fix checkpatch warning for CamelCase
> media: davinci: vpbe: enable vpbe for fbdev addition
> davinci: vpbe: add fbdev driver
> ARM: davinci: dm355: enable fbdev driver
> ARM: davinci: dm365: enable fbdev driver
> ARM: davinci: dm644x: enable fbdev driver
>
> arch/arm/mach-davinci/dm355.c | 24 +-
> arch/arm/mach-davinci/dm365.c | 10 +
> arch/arm/mach-davinci/dm644x.c | 10 +
> drivers/media/platform/davinci/vpbe_display.c | 8 +-
> drivers/media/platform/davinci/vpbe_osd.c | 820 ++++++++-
> drivers/media/platform/davinci/vpbe_venc.c | 43 +
> drivers/video/Kconfig | 12 +
> drivers/video/Makefile | 1 +
> drivers/video/davincifb.c | 2523 ++++++++++++++++++++++
> drivers/video/davincifb.h | 194 ++
> include/media/davinci/vpbe_osd.h | 66 +-
> include/media/davinci/vpbe_venc.h | 21 +
> 12 files changed, 3702 insertions(+), 30 deletions(-)
> create mode 100644 drivers/video/davincifb.c
> create mode 100644 drivers/video/davincifb.h
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-24 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 12:00 [PATCH 0/6] Davinci fbdev driver and enable it for DMx platform Prabhakar Lad
2013-04-24 12:00 ` [PATCH 1/6] media: davinci: vpbe: fix checkpatch warning for CamelCase Prabhakar Lad
2013-04-24 12:00 ` [PATCH 2/6] media: davinci: vpbe: enable vpbe for fbdev addition Prabhakar Lad
2013-04-24 12:00 ` [PATCH 3/6] davinci: vpbe: add fbdev driver Prabhakar Lad
2013-04-24 12:00 ` [PATCH 4/6] ARM: davinci: dm355: enable " Prabhakar Lad
2013-04-24 12:00 ` [PATCH 5/6] ARM: davinci: dm365: " Prabhakar Lad
2013-04-24 12:00 ` [PATCH 6/6] ARM: davinci: dm644x: " Prabhakar Lad
2013-04-24 21:02 ` Laurent Pinchart [this message]
2013-04-26 5:46 ` [PATCH 0/6] Davinci fbdev driver and enable it for DMx platform Prabhakar Lad
2013-05-03 9:55 ` Sekhar Nori
2013-05-03 10:15 ` Prabhakar Lad
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=1780031.B4OAypccep@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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).