From: "Ong, Hean Loong" <hean.loong.ong@intel.com>
To: "dinguyen@kernel.org" <dinguyen@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"airlied@linux.ie" <airlied@linux.ie>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"See, Chin Liang" <chin.liang.see@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Vandervennet, Yves" <yves.vandervennet@intel.com>
Subject: Re: [PATCH10 0/3] Intel FPGA Video and Image Processing Suite
Date: Wed, 15 Aug 2018 01:42:45 +0000 [thread overview]
Message-ID: <1534297365.3035.0.camel@intel.com> (raw)
In-Reply-To: <3720ba74-947a-1b5d-5f5b-1ef03d5941aa@kernel.org>
On Tue, 2018-08-14 at 10:48 -0500, Dinh Nguyen wrote:
>
> On 08/14/2018 03:57 AM, Hean-Loong, Ong wrote:
> >
> > 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.
> This driver doesn't have to ARM specific does it?
>
> >
> >
> > 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 | 9 +
> > drivers/gpu/drm/ivip/intel_vip_conn.c | 95
> > ++++++++++
> > drivers/gpu/drm/ivip/intel_vip_core.c | 161
> > ++++++++++++++++
> > drivers/gpu/drm/ivip/intel_vip_drv.h | 52 ++++++
> > drivers/gpu/drm/ivip/intel_vip_of.c | 193
> > ++++++++++++++++++++
> > 10 files changed, 595 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
> >
> Can you clarify your commit header? What is "PATCH10", is it version
> 10?
> If so, it should be "PATCHv10".
>
> You're also missing a few other maintainers in your CC list, the "DRM
> DRIVERS AND MISC GPU PATCHES" people.
>
Noted
> Dinh
prev parent reply other threads:[~2018-08-15 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 8:57 [PATCH10 0/3] Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
2018-08-14 8:57 ` [PATCH10 1/3] ARM:dt-bindings:display " Hean-Loong, Ong
2018-08-14 14:43 ` Rob Herring
2018-08-14 8:57 ` [PATCH10 2/3] ARM:socfpga-defconfig " Hean-Loong, Ong
2018-08-14 8:57 ` [PATCH10 3/3] ARM:drm ivip " Hean-Loong, Ong
2018-08-14 15:46 ` Dinh Nguyen
2018-08-15 1:44 ` Ong, Hean Loong
2018-08-15 12:26 ` Noralf Trønnes
2018-08-16 8:33 ` Ong, Hean Loong
2018-08-16 9:10 ` Noralf Trønnes
2018-08-14 15:48 ` [PATCH10 0/3] " Dinh Nguyen
2018-08-15 1:42 ` Ong, Hean Loong [this message]
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=1534297365.3035.0.camel@intel.com \
--to=hean.loong.ong@intel.com \
--cc=airlied@linux.ie \
--cc=chin.liang.see@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=robh+dt@kernel.org \
--cc=yves.vandervennet@intel.com \
/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).