From: Hanjun Guo <guohanjun@huawei.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/3] Hisilicon graphic driver
Date: Sun, 08 Nov 2015 07:55:00 +0000 [thread overview]
Message-ID: <563EFFD4.5090708@huawei.com> (raw)
In-Reply-To: <BLU437-SMTP248CA33D65A31EAE12675CC32B0@phx.gbl>
On 2015/11/3 21:54, Rongrong Zou wrote:
> From: Rongrong Zou <rongrongchau@163.com>
>
> Hi1710 chip have a graphic modue with 2d acceleration, this driver support
> the graphic module.
>
> Rongrong Zou (3):
> Hisilicon graphic driver: add fbdev support to hisilicon hi1710
> graphic chip
> Hisilicon graphic driver: add hardware cursor support to hisilicon
> hi1710 graphi chip
> Hisilicon graphic driver: add 2d acceleration to hisilicon hi1710
> graphic chip
Fixed the conflicts and tested on lemon board, and it works as expected,
queue up for next hulk release.
Thanks
Hanjun
>
> MAINTAINERS | 7 +
> drivers/video/fbdev/Kconfig | 14 +
> drivers/video/fbdev/Makefile | 2 +-
> drivers/video/fbdev/hisilicon/Makefile | 6 +
> drivers/video/fbdev/hisilicon/hisi_accel.c | 382 ++++++++
> drivers/video/fbdev/hisilicon/hisi_accel.h | 62 ++
> drivers/video/fbdev/hisilicon/hisi_chip.c | 131 +++
> drivers/video/fbdev/hisilicon/hisi_chip.h | 62 ++
> drivers/video/fbdev/hisilicon/hisi_cursor.c | 121 +++
> drivers/video/fbdev/hisilicon/hisi_cursor.h | 11 +
> drivers/video/fbdev/hisilicon/hisi_drv.c | 1326 +++++++++++++++++++++++++++
> drivers/video/fbdev/hisilicon/hisi_drv.h | 181 ++++
> drivers/video/fbdev/hisilicon/hisi_help.h | 64 ++
> drivers/video/fbdev/hisilicon/hisi_hw.c | 314 +++++++
> drivers/video/fbdev/hisilicon/hisi_hw.h | 95 ++
> drivers/video/fbdev/hisilicon/hisi_mode.c | 286 ++++++
> drivers/video/fbdev/hisilicon/hisi_mode.h | 39 +
> drivers/video/fbdev/hisilicon/hisi_power.c | 106 +++
> drivers/video/fbdev/hisilicon/hisi_power.h | 18 +
> drivers/video/fbdev/hisilicon/hisi_reg.h | 418 +++++++++
> 20 files changed, 3644 insertions(+), 1 deletion(-)
> create mode 100644 drivers/video/fbdev/hisilicon/Makefile
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_accel.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_accel.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_chip.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_chip.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_cursor.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_cursor.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_drv.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_drv.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_help.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_hw.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_hw.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_mode.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_mode.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_power.c
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_power.h
> create mode 100644 drivers/video/fbdev/hisilicon/hisi_reg.h
>
next prev parent reply other threads:[~2015-11-08 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 13:54 [PATCH 0/3] Hisilicon graphic driver Rongrong Zou
2015-11-08 7:55 ` Hanjun Guo [this message]
2015-11-08 8:01 ` Hanjun Guo
2015-11-10 11:38 ` Tomi Valkeinen
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=563EFFD4.5090708@huawei.com \
--to=guohanjun@huawei.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).