From: "Hean-Loong, Ong" <hean.loong.ong@intel.com>
To: "Rob Herring" <robh+dt@kernel.org>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Rienk de Jong" <rienk.dejong@quest-innovations.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, hean.loong.ong@intel.com,
chin.liang.see@intel.com, Ong@vger.kernel.org
Subject: [PATCHv11 0/3] Intel FPGA Video and Image Processing Suite
Date: Mon, 11 Feb 2019 10:11:07 +0800 [thread overview]
Message-ID: <20190211021110.2717-1-hean.loong.ong@intel.com> (raw)
From: Ong, Hean Loong <hean.loong.ong@intel.com>
The FPGA FrameBuffer Soft IP could be seen as the GPU and the DRM driver
patch here is allocating memory for information to be streamed from the
ARM/Linux to the display port.
Basically the driver just wraps the information such as the pixels
to be drawn by the FPGA FrameBuffer 2.
The piece of hardware in discussion is the SoC FPGA where Linux runs on
the ARM chip and the FGPA is driven by its NIOS soft core with its own
proprietary firmware.
For example the application from the ARM Linux would have to write
information on the /dev/fb0 with the information stored in the
SDRAM to be fetched by the FPGA framebuffer IP and displayed
on the Display Port Monitor.
Ong Hean Loong (2):
ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite
ARM:drm ivip Intel FPGA Video and Image Processing Suite
Ong, Hean Loong (1):
ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite
.../devicetree/bindings/display/altr,vip-fb2.txt | 63 +++++++
arch/arm/configs/socfpga_defconfig | 5 +
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/ivip/Kconfig | 14 ++
drivers/gpu/drm/ivip/Makefile | 7 +
drivers/gpu/drm/ivip/intel_vip_conn.c | 87 ++++++++++
drivers/gpu/drm/ivip/intel_vip_core.c | 152 +++++++++++++++++
drivers/gpu/drm/ivip/intel_vip_drv.h | 40 +++++
drivers/gpu/drm/ivip/intel_vip_of.c | 177 ++++++++++++++++++++
10 files changed, 548 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/display/altr,vip-fb2.txt
create mode 100644 drivers/gpu/drm/ivip/Kconfig
create mode 100644 drivers/gpu/drm/ivip/Makefile
create mode 100644 drivers/gpu/drm/ivip/intel_vip_conn.c
create mode 100644 drivers/gpu/drm/ivip/intel_vip_core.c
create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h
create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c
next reply other threads:[~2019-02-11 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 2:11 Hean-Loong, Ong [this message]
2019-02-11 2:11 ` [PATCHv11 1/3] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
2019-02-11 2:11 ` Hean-Loong, Ong
2019-02-11 2:11 ` [PATCHv11 2/3] ARM:socfpga-defconfig " Hean-Loong, Ong
2019-02-11 2:11 ` Hean-Loong, Ong
2019-02-11 2:11 ` [PATCHv11 3/3] ARM:drm ivip " Hean-Loong, Ong
2019-02-11 2:11 ` Hean-Loong, Ong
2019-02-28 14:10 ` Daniel Vetter
2019-02-28 14:10 ` Daniel Vetter
2019-02-28 14:10 ` Daniel Vetter
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=20190211021110.2717-1-hean.loong.ong@intel.com \
--to=hean.loong.ong@intel.com \
--cc=Ong@vger.kernel.org \
--cc=chin.liang.see@intel.com \
--cc=daniel.vetter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=rienk.dejong@quest-innovations.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.