From: Jun Nie <niej0001@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/8] pxa: frame buffer support both pxa168 and pxa910
Date: Tue, 10 Nov 2009 08:12:25 +0000 [thread overview]
Message-ID: <7c34ac520911100012l43680a5fn1ffa2f44d8c27801@mail.gmail.com> (raw)
From ce9b930b389f6b2ecbdf0102a6055f737c56979a Mon Sep 17 00:00:00 2001
From: Jun Nie <njun@marvell.com>
Date: Tue, 10 Nov 2009 09:43:57 +0800
Subject: [PATCH] pxa: frame buffer support both pxa168 and pxa910
Signed-off-by: Jun Nie <njun@marvell.com>
---
drivers/video/pxa168fb.c | 6 ++++++
include/video/pxa168fb.h | 3 +++
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/video/pxa168fb.c b/drivers/video/pxa168fb.c
index 55c69a1..ca0a4d3 100644
--- a/drivers/video/pxa168fb.c
+++ b/drivers/video/pxa168fb.c
@@ -879,12 +879,18 @@ failed:
return ret;
}
+ static const struct platform_device_id mmpfb_id_table[] = {
+ {"pxa168-fb", PXA168_FB},
+ {"pxa910-fb", PXA910_FB},
+ };
+
static struct platform_driver pxa168fb_driver = {
.driver = {
.name = "pxa168-fb",
.owner = THIS_MODULE,
},
.probe = pxa168fb_probe,
+ .id_table = mmpfb_id_table,
};
static int __devinit pxa168fb_init(void)
diff --git a/include/video/pxa168fb.h b/include/video/pxa168fb.h
index efbe469..41f21c5 100644
--- a/include/video/pxa168fb.h
+++ b/include/video/pxa168fb.h
@@ -86,6 +86,9 @@
#define PIX_FMT_PSEUDOCOLOR 20
#define PIX_FMT_UYVY422PACK (0x1000|PIX_FMT_YUV422PACK)
+#define PXA168_FB 0x0168
+#define PXA910_FB 0x0910
+
/*
* PXA LCD controller private state.
*/
--
1.5.4.3
next reply other threads:[~2009-11-10 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 8:12 Jun Nie [this message]
2009-11-12 2:18 ` [PATCH 5/8] pxa: frame buffer support both pxa168 and pxa910 Jun Nie
2009-11-16 9:34 ` Jun Nie
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=7c34ac520911100012l43680a5fn1ffa2f44d8c27801@mail.gmail.com \
--to=niej0001@gmail.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).