devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
To: daniel.vetter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	jani.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	dinguyen-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Ong Hean Loong
	<hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [PATCHv3 0/3] Intel FPGA VIP Frame Buffer II drm driver
Date: Tue, 11 Jul 2017 13:51:59 +0800	[thread overview]
Message-ID: <1499752322-9196-1-git-send-email-hean.loong.ong@intel.com> (raw)

From: Ong Hean Loong <hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

 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 (3):
  dt-bindings: display: Intel FPGA VIP drm driver Devicetree bindings
  ARM: socfpga: drm driver updates in socfpga_defconfig
  ARM: drm: Intel FPGA VIP Frame Buffer II drm driver

 .../devicetree/bindings/display/altr,vip-fb2.txt   |  41 +++++
 arch/arm/configs/socfpga_defconfig                 |   6 +
 drivers/gpu/drm/Kconfig                            |   2 +
 drivers/gpu/drm/Makefile                           |   1 +
 drivers/gpu/drm/ivip/Kconfig                       |  13 ++
 drivers/gpu/drm/ivip/Makefile                      |   9 +
 drivers/gpu/drm/ivip/intel_vip_conn.c              |  96 ++++++++++
 drivers/gpu/drm/ivip/intel_vip_core.c              | 182 +++++++++++++++++++
 drivers/gpu/drm/ivip/intel_vip_drv.h               |  54 ++++++
 drivers/gpu/drm/ivip/intel_vip_of.c                | 202 +++++++++++++++++++++
 10 files changed, 606 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_core.c
 create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h
 create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c

-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-07-11  5:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11  5:51 hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w [this message]
     [not found] ` <1499752322-9196-1-git-send-email-hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-07-11  5:52   ` [PATCHv3 1/3] dt-bindings: display: Intel FPGA VIP drm driver Devicetree bindings hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w
2017-07-11  5:52   ` [PATCHv3 2/3] ARM: socfpga: drm driver updates in socfpga_defconfig hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w
2017-07-11  5:52   ` [PATCHv3 3/3] ARM: drm: Intel FPGA VIP Frame Buffer II drm driver hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w
  -- strict thread matches above, loose matches on Subject: below --
2017-07-13  1:40 [PATCHv3 0/3] " hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w

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=1499752322-9196-1-git-send-email-hean.loong.ong@intel.com \
    --to=hean.loong.ong-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=daniel.vetter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dinguyen-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=jani.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).