From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tom Gall <tom.gall@linaro.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Dave Airlie <airlied@redhat.com>,
Thierry Reding <treding@nvidia.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [RFC] How implement Secure Data Path ?
Date: Wed, 06 May 2015 03:50:13 +0300 [thread overview]
Message-ID: <6502790.6UvsMdppjg@avalon> (raw)
In-Reply-To: <20150505162752.GA12132@infradead.org>
On Tuesday 05 May 2015 09:27:52 Christoph Hellwig wrote:
> On Tue, May 05, 2015 at 05:39:57PM +0200, Benjamin Gaignard wrote:
> > Since few months I'm looking for Linaro to how do Secure Data Path (SPD).
> > I have tried and implemented multiple thinks but I always facing
> > architecture issues so I would like to get your help to solve the
> > problem.
> >
> > First what is Secure Data Path ? SDP is a set of hardware features to
> > garanty that some memories regions could only be read and/or write by
> > specific hardware IPs. You can imagine it as a kind of memory firewall
> > which grant/revoke accesses to memory per devices. Firewall configuration
> > must be done in a trusted environment: for ARM architecture we plan to
> > use OP-TEE + a trusted application to do that.
> >
> > One typical use case for SDP in a video playback which involve those
> > elements: decrypt -> video decoder -> transform -> display
>
> Sounds like a good enough reason not to implement it ever.
The irony of it is to post an RFC on they day before
http://www.defectivebydesign.org/dayagainstdrm/ :-)
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Rob Clark <robdclark@gmail.com>,
Thierry Reding <treding@nvidia.com>,
Dave Airlie <airlied@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Tom Gall <tom.gall@linaro.org>
Subject: Re: [RFC] How implement Secure Data Path ?
Date: Wed, 06 May 2015 03:50:13 +0300 [thread overview]
Message-ID: <6502790.6UvsMdppjg@avalon> (raw)
In-Reply-To: <20150505162752.GA12132@infradead.org>
On Tuesday 05 May 2015 09:27:52 Christoph Hellwig wrote:
> On Tue, May 05, 2015 at 05:39:57PM +0200, Benjamin Gaignard wrote:
> > Since few months I'm looking for Linaro to how do Secure Data Path (SPD).
> > I have tried and implemented multiple thinks but I always facing
> > architecture issues so I would like to get your help to solve the
> > problem.
> >
> > First what is Secure Data Path ? SDP is a set of hardware features to
> > garanty that some memories regions could only be read and/or write by
> > specific hardware IPs. You can imagine it as a kind of memory firewall
> > which grant/revoke accesses to memory per devices. Firewall configuration
> > must be done in a trusted environment: for ARM architecture we plan to
> > use OP-TEE + a trusted application to do that.
> >
> > One typical use case for SDP in a video playback which involve those
> > elements: decrypt -> video decoder -> transform -> display
>
> Sounds like a good enough reason not to implement it ever.
The irony of it is to post an RFC on they day before
http://www.defectivebydesign.org/dayagainstdrm/ :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-05-06 0:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 15:39 [RFC] How implement Secure Data Path ? Benjamin Gaignard
2015-05-05 15:39 ` Benjamin Gaignard
2015-05-05 16:27 ` Christoph Hellwig
2015-05-05 16:27 ` Christoph Hellwig
2015-05-06 0:50 ` Laurent Pinchart [this message]
2015-05-06 0:50 ` Laurent Pinchart
2015-05-06 8:37 ` Daniel Vetter
2015-05-06 8:37 ` Daniel Vetter
2015-05-05 16:54 ` One Thousand Gnomes
2015-05-06 8:35 ` Daniel Vetter
2015-05-06 8:49 ` Hans Verkuil
2015-05-06 8:49 ` Hans Verkuil
2015-05-06 9:19 ` Thierry Reding
2015-05-06 9:19 ` Thierry Reding
2015-05-06 13:15 ` Daniel Vetter
2015-05-07 13:22 ` Thierry Reding
2015-05-07 13:22 ` Thierry Reding
2015-05-07 13:52 ` Daniel Vetter
2015-05-07 13:52 ` Daniel Vetter
2015-05-07 16:40 ` One Thousand Gnomes
2015-05-08 8:37 ` Daniel Vetter
2015-05-08 8:55 ` Enrico Weigelt, metux IT consult
2015-05-08 19:18 ` One Thousand Gnomes
2015-05-12 8:46 ` Benjamin Gaignard
2015-05-12 8:46 ` Benjamin Gaignard
2015-05-06 9:22 ` Benjamin Gaignard
2015-05-06 9:22 ` Benjamin Gaignard
2015-05-06 11:29 ` Rob Clark
2015-05-06 11:29 ` Rob Clark
2015-05-07 14:41 ` Thierry Reding
2015-05-07 14:41 ` Thierry Reding
2015-05-06 8:46 ` Benjamin Gaignard
2015-05-06 8:46 ` Benjamin Gaignard
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=6502790.6UvsMdppjg@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@redhat.com \
--cc=benjamin.gaignard@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=tom.gall@linaro.org \
--cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.