From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Pinchart Subject: Re: [RFC] How implement Secure Data Path ? Date: Wed, 06 May 2015 03:50:13 +0300 Message-ID: <6502790.6UvsMdppjg@avalon> References: <20150505162752.GA12132@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from galahad.ideasonboard.com (galahad.ideasonboard.com [185.26.127.97]) by gabe.freedesktop.org (Postfix) with ESMTP id E11506E2F3 for ; Tue, 5 May 2015 17:50:19 -0700 (PDT) In-Reply-To: <20150505162752.GA12132@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Christoph Hellwig Cc: Tom Gall , Daniel Vetter , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Benjamin Gaignard , Dave Airlie , Thierry Reding , "linux-media@vger.kernel.org" List-Id: dri-devel@lists.freedesktop.org T24gVHVlc2RheSAwNSBNYXkgMjAxNSAwOToyNzo1MiBDaHJpc3RvcGggSGVsbHdpZyB3cm90ZToK PiBPbiBUdWUsIE1heSAwNSwgMjAxNSBhdCAwNTozOTo1N1BNICswMjAwLCBCZW5qYW1pbiBHYWln bmFyZCB3cm90ZToKPiA+IFNpbmNlIGZldyBtb250aHMgSSdtIGxvb2tpbmcgZm9yIExpbmFybyB0 byBob3cgZG8gU2VjdXJlIERhdGEgUGF0aCAoU1BEKS4KPiA+IEkgaGF2ZSB0cmllZCBhbmQgaW1w bGVtZW50ZWQgbXVsdGlwbGUgdGhpbmtzIGJ1dCBJIGFsd2F5cyBmYWNpbmcKPiA+IGFyY2hpdGVj dHVyZSBpc3N1ZXMgc28gSSB3b3VsZCBsaWtlIHRvIGdldCB5b3VyIGhlbHAgdG8gc29sdmUgdGhl Cj4gPiBwcm9ibGVtLgo+ID4gCj4gPiBGaXJzdCB3aGF0IGlzIFNlY3VyZSBEYXRhIFBhdGggPyBT RFAgaXMgYSBzZXQgb2YgaGFyZHdhcmUgZmVhdHVyZXMgdG8KPiA+IGdhcmFudHkgdGhhdCBzb21l IG1lbW9yaWVzIHJlZ2lvbnMgY291bGQgb25seSBiZSByZWFkIGFuZC9vciB3cml0ZSBieQo+ID4g c3BlY2lmaWMgaGFyZHdhcmUgSVBzLiBZb3UgY2FuIGltYWdpbmUgaXQgYXMgYSBraW5kIG9mIG1l bW9yeSBmaXJld2FsbAo+ID4gd2hpY2ggZ3JhbnQvcmV2b2tlIGFjY2Vzc2VzIHRvIG1lbW9yeSBw ZXIgZGV2aWNlcy4gRmlyZXdhbGwgY29uZmlndXJhdGlvbgo+ID4gbXVzdCBiZSBkb25lIGluIGEg dHJ1c3RlZCBlbnZpcm9ubWVudDogZm9yIEFSTSBhcmNoaXRlY3R1cmUgd2UgcGxhbiB0bwo+ID4g dXNlIE9QLVRFRSArIGEgdHJ1c3RlZCBhcHBsaWNhdGlvbiB0byBkbyB0aGF0Lgo+ID4gCj4gPiBP bmUgdHlwaWNhbCB1c2UgY2FzZSBmb3IgU0RQIGluIGEgdmlkZW8gcGxheWJhY2sgd2hpY2ggaW52 b2x2ZSB0aG9zZQo+ID4gZWxlbWVudHM6IGRlY3J5cHQgLT4gdmlkZW8gZGVjb2RlciAtPiB0cmFu c2Zvcm0gLT4gZGlzcGxheQo+IAo+IFNvdW5kcyBsaWtlIGEgZ29vZCBlbm91Z2ggcmVhc29uIG5v dCB0byBpbXBsZW1lbnQgaXQgZXZlci4KClRoZSBpcm9ueSBvZiBpdCBpcyB0byBwb3N0IGFuIFJG QyBvbiB0aGV5IGRheSBiZWZvcmUgCmh0dHA6Ly93d3cuZGVmZWN0aXZlYnlkZXNpZ24ub3JnL2Rh eWFnYWluc3Rkcm0vIDotKQoKLS0gClJlZ2FyZHMsCgpMYXVyZW50IFBpbmNoYXJ0CgpfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpkcmktZGV2ZWwgbWFpbGlu ZyBsaXN0CmRyaS1kZXZlbEBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cDovL2xpc3RzLmZyZWVk ZXNrdG9wLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RyaS1kZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from galahad.ideasonboard.com ([185.26.127.97]:43192 "EHLO galahad.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753558AbbEFAuS (ORCPT ); Tue, 5 May 2015 20:50:18 -0400 From: Laurent Pinchart To: Christoph Hellwig Cc: Benjamin Gaignard , "linux-media@vger.kernel.org" , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Hans Verkuil , Daniel Vetter , Rob Clark , Thierry Reding , Dave Airlie , Sumit Semwal , Tom Gall Subject: Re: [RFC] How implement Secure Data Path ? Date: Wed, 06 May 2015 03:50:13 +0300 Message-ID: <6502790.6UvsMdppjg@avalon> In-Reply-To: <20150505162752.GA12132@infradead.org> References: <20150505162752.GA12132@infradead.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-media-owner@vger.kernel.org List-ID: 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