mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pratyush Brahma <quic_pbrahma@quicinc.com>
To: <sumit.semwal@linaro.org>, <benjamin.gaignard@collabora.com>,
	<Brian.Starkey@arm.com>, <jstultz@google.com>,
	<tjmercier@google.com>, <christian.koenig@amd.com>,
	<linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
	<linaro-mm-sig@lists.linaro.org>, <linux-kernel@vger.kernel.org>,
	<quic_guptap@quicinc.com>
Cc: Vijayanand Jitta <quic_vjitta@quicinc.com>
Subject: [PATCH 0/2] Add qcom secure heaps
Date: Wed, 22 Nov 2023 19:17:45 +0530	[thread overview]
Message-ID: <cover.1700544802.git.quic_vjitta@quicinc.com> (raw)
In-Reply-To: <y>

From: Vijayanand Jitta <quic_vjitta@quicinc.com>

This patch series is based on mtk patch series [1] of
adding secure heap support.

This patch series adds support for qcom secure heaps which
include secure cma heap and secure system heap, this does
use qcom_scm_assign_mem to secure the memory.

Video would be the user of these heaps and the corresponding
VMIDs are also as added as part of these.


[1] https://lore.kernel.org/linux-arm-kernel/20231111111559.8218-2-yong.wu@mediatek.com/T/

Vijayanand Jitta (2):
  dma-buf: heaps: secure_heap: Add secure ops for CMA heap
  dma-buf: heaps: secure_heap: Add qcom secure system heap

 drivers/dma-buf/heaps/secure_heap.c | 207 +++++++++++++++++++++++++++-
 1 file changed, 204 insertions(+), 3 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-11-22 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 13:47 Pratyush Brahma [this message]
2023-11-22 13:47 ` [PATCH 1/2] dma-buf: heaps: secure_heap: Add secure ops for CMA heap Pratyush Brahma
2023-11-24  7:43   ` Pavan Kondeti
2023-11-22 13:47 ` [PATCH 2/2] dma-buf: heaps: secure_heap: Add qcom secure system heap Pratyush Brahma
2024-02-20 18:23   ` Elliot Berman

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=cover.1700544802.git.quic_vjitta@quicinc.com \
    --to=quic_pbrahma@quicinc.com \
    --cc=Brian.Starkey@arm.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jstultz@google.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=quic_guptap@quicinc.com \
    --cc=quic_vjitta@quicinc.com \
    --cc=sumit.semwal@linaro.org \
    --cc=tjmercier@google.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

all inboxes | Powered by JetHome®