dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ong, Hean Loong" <hean.loong.ong@intel.com>
To: "laurent.pinchart@ideasonboard.com" <laurent.pinchart@ideasonboard.com>
Cc: "dinguyen@kernel.org" <dinguyen@kernel.org>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCHv6 1/3] ARM:dt-bindings Intel FPGA Video and Image Processing Suite
Date: Mon, 4 Sep 2017 06:09:11 +0000	[thread overview]
Message-ID: <1504505350.2419.3.camel@intel.com> (raw)
In-Reply-To: <1503896807.2390.0.camel@intel.com>

Hi Laurent,

On Mon, 2017-08-28 at 13:06 +0800, Ong, Hean Loong wrote:
> Hi Laurent,
> 
> On Thu, 2017-08-24 at 12:39 +0300, Laurent Pinchart wrote:
> > 
> > Hi Hean Loong,
> > 
> > On Thursday, 24 August 2017 08:41:50 EEST Ong, Hean Loong wrote:
> > > 
> > > 
> > > Hi Laurent,
> > > 
> > > I removed the examples for the HDMI in the draft below. The
> > > connections
> > > between the VIP and Display Port IP or any display connector are
> > > determined by HW logic. There are currently no SW defined
> > > encoders
> > > or
> > > connectors that is connected to the AVALON-ST other than the
> > > Intel
> > > VIP
> > > Frame Buffer II. Therefore there are no examples for the Display
> > > Port
> > > encoder and connector.
> > But there must be an encoder, even if its default configuration
> > makes
> > it 
> > usable without a softwarer driver at the moment. As the encoder is
> > there in 
> > hardware, it should be described in DT.
> > 
> I attach some links regarding the simple example designs for the
> Display Port IP
> 
> The link below has a example design of how the VIP is built along
> with
> the Display Port IP 
> into the FPGA connected to the DDR RAM accessed by ARM or any
> controller. Please look at the
> Introduction section of the link below
> http://www.alterawiki.com/wiki/DisplayPort_Design_Example_14.0_(RX_an
> d_
> TX)#DisplayPort_IP_Core
> 
> The proposed design in the link above and the design we are
> implementing are almost the same (FPGA part)
> That the Intel(Altera) FPGA VIP is the sole interface for the ARM
> controller to connect to via memory mapping
> on the DDR
> 
> Please go to Source Functional Description section in the PDF below.
> It
> has information
> on how the encoder is built for the FPGA design of the Display Port
> https://www.altera.com/ja_JP/pdfs/literature/ug/ug_displayport.pdf
> 
> More information on the Display Port IP encoder could be found in the
> link below.
> The Tx Transceiver interface has some information on how the source
> clocks works in
> the FPGA tranceiver
> https://www.altera.com/documentation/hco1410462777019.html#hco1410462
> 32
> 3311

Would the information provided in the above links suffice to explain
the relationship between DDR, VIP and Display Port IP ?

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-09-04  6:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  6:49 [PATCHv6 0/3] Hean-Loong, Ong
2017-08-11  6:49 ` [PATCHv6 1/3] ARM:dt-bindings Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
     [not found]   ` <1502434187-6407-2-git-send-email-hean.loong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-08-17 15:22     ` Rob Herring
2017-08-18  0:56       ` Ong, Hean Loong
2017-08-11  6:49 ` [PATCHv6 2/3] ARM:socfpga-defconfig " Hean-Loong, Ong
2017-08-11  6:49 ` [PATCHv6 3/3] ARM:drm ivip " Hean-Loong, Ong
2017-08-11 15:21   ` Randy Dunlap
     [not found]     ` <b3505a39-9fa9-c993-15cb-d643a34f58a9-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-08-14  2:27       ` Ong, Hean Loong
     [not found] ` <2740499.pDDaZTb32r@avalon>
     [not found]   ` <1503045283.2075.8.camel@intel.com>
2017-08-18 13:11     ` [PATCHv6 1/3] ARM:dt-bindings " Laurent Pinchart
2017-08-21  1:40       ` Ong, Hean Loong
2017-08-21  5:09         ` Laurent Pinchart
2017-08-24  5:41           ` Ong, Hean Loong
2017-08-24  9:39             ` Laurent Pinchart
2017-08-25  1:21               ` Ong, Hean Loong
2017-08-25  9:32                 ` Laurent Pinchart
2017-08-28  5:06               ` Ong, Hean Loong
2017-09-04  6:09                 ` Ong, Hean Loong [this message]
2017-09-12 22:47                   ` Laurent Pinchart

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=1504505350.2419.3.camel@intel.com \
    --to=hean.loong.ong@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dinguyen@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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