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@ffwll.ch>,
Randy Dunlap <rdunlap@infradead.org>
Cc: devicetree@vger.kernel.org, hean.loong.ong@intel.com,
chin.liang.see@intel.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCHv15 0/3] Intel FPGA Video and Image Processing Suite
Date: Fri, 7 Jun 2019 22:28:24 +0800 [thread overview]
Message-ID: <20190607142827.329-1-hean.loong.ong@intel.com> (raw)
From: Hean-Loong Ong <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 Sodt IP 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 Framebuffer 2 Soft IP and displayed
on the Display Port Monitor.
Reviewed and ACKed need to merge this into drm-misc
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Rob Herring <robh@kernel.org>
Ong Hean Loong (1):
ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite
Ong, Hean Loong (2):
ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite
ARM:drm ivip Intel FPGA Video and Image Processing Suite
.../bindings/display/altr,vip-fb2.txt | 63 ++++
MAINTAINERS | 9 +
arch/arm/configs/socfpga_defconfig | 8 +
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/ivip/Kconfig | 14 +
drivers/gpu/drm/ivip/Makefile | 6 +
drivers/gpu/drm/ivip/intel_vip_conn.c | 93 +++++
drivers/gpu/drm/ivip/intel_vip_drv.c | 335 ++++++++++++++++++
drivers/gpu/drm/ivip/intel_vip_drv.h | 73 ++++
10 files changed, 604 insertions(+)
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_drv.c
create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-06-07 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 14:28 Hean-Loong, Ong [this message]
2019-06-07 14:28 ` [PATCHv15 1/3] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
-- strict thread matches above, loose matches on Subject: below --
2019-06-07 14:30 [PATCHv15 0/3] " Hean-Loong, Ong
2019-03-15 14:54 Hean-Loong Ong
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=20190607142827.329-1-hean.loong.ong@intel.com \
--to=hean.loong.ong@intel.com \
--cc=chin.liang.see@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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=rdunlap@infradead.org \
--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 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).