From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jithin T Raj <jithin.t@tataelxsi.co.in>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"laurent.pinchart+renesas@ideasonboard.com"
<laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: About VSPD
Date: Fri, 06 Jan 2017 16:42:54 +0200 [thread overview]
Message-ID: <2306529.eAzpfA7p5A@avalon> (raw)
In-Reply-To: <HK2PR04MB122088542BF30F00286A7C30D8630@HK2PR04MB1220.apcprd04.prod.outlook.com>
Hello Jithin,
On Friday 06 Jan 2017 07:15:27 Jithin T Raj wrote:
> hello Laurent and all,
>
> Can anybody give me an insight to VSPD .Recently I am going through
> the term VSPD..Is it associated with Display Unit ? ..It will be a help if
> someone share some links about VSPD..I am a beginner in both kernel and
> RCar families..
The VSP is a memory-to-memory image processor than can perform operations such
as format conversion, scaling, blending, ... There are multiple VSP instances
on R-Car Gen2 and Gen3 SoCs, whose number and features depend on the
particular SoC. The VSPD is a VSP type designed for display operation that can
feed its output directly to the display in addition to writing it to memory
like all other VSPs. On R-Car Gen3 SoCs usage of the VSPD for display is
mandatory, so the VSPD is handled automatically by the DU driver and isn't
visible to userspace. On R-Car Gen2 SocS usage of the VSPD for display os
optional, so the VSPD is exposed to userspace through the V4L2 API. Connecting
the VSPD output directly to the display on R-Car Gen2 currently requires out-
of-tree patches (see
http://comments.gmane.org/gmane.comp.video.dri.devel/127526).
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2017-01-06 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 7:15 About VSPD Jithin T Raj
2017-01-06 14:42 ` Laurent Pinchart [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=2306529.eAzpfA7p5A@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=jithin.t@tataelxsi.co.in \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.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