From: Sumit Garg <sumit.garg@kernel.org>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH v6 05/10] tee: implement restricted DMA-heap
Date: Tue, 01 Apr 2025 13:28:48 +0530 [thread overview]
Message-ID: <Z-ucuPzwz4IqVTgb@sumit-X1> (raw)
In-Reply-To: < <CAHUa44GjpHT5Nqo+Ar5jNYNPV-YJQYpLTCf=7oJ1o0VjP-t0nA@mail.gmail.com>>
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
On Tue, Mar 25, 2025 at 11:55:46AM +0100, Jens Wiklander wrote:
> Hi Sumit,
>
<snip>
>
> >
> > > +
> > > +#include "tee_private.h"
> > > +
> > > +struct tee_dma_heap {
> > > + struct dma_heap *heap;
> > > + enum tee_dma_heap_id id;
> > > + struct tee_rstmem_pool *pool;
> > > + struct tee_device *teedev;
> > > + /* Protects pool and teedev above */
> > > + struct mutex mu;
> > > +};
> > > +
> > > +struct tee_heap_buffer {
> > > + struct tee_rstmem_pool *pool;
> > > + struct tee_device *teedev;
> > > + size_t size;
> > > + size_t offs;
> > > + struct sg_table table;
> > > +};
> > > +
> > > +struct tee_heap_attachment {
> > > + struct sg_table table;
> > > + struct device *dev;
> > > +};
> > > +
> > > +struct tee_rstmem_static_pool {
> > > + struct tee_rstmem_pool pool;
> > > + struct gen_pool *gen_pool;
> > > + phys_addr_t pa_base;
> > > +};
> > > +
> > > +#if !IS_MODULE(CONFIG_TEE) && IS_ENABLED(CONFIG_DMABUF_HEAPS)
> >
> > Can this dependency rather be better managed via Kconfig?
>
> This was the easiest yet somewhat flexible solution I could find. If
> you have something better, let's use that instead.
>
--- a/drivers/tee/optee/Kconfig
+++ b/drivers/tee/optee/Kconfig
@@ -5,6 +5,7 @@ config OPTEE
depends on HAVE_ARM_SMCCC
depends on MMU
depends on RPMB || !RPMB
+ select DMABUF_HEAPS
help
This implements the OP-TEE Trusted Execution Environment (TEE)
driver.
-Sumit
next parent reply other threads:[~2025-04-01 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] < <CAHUa44GjpHT5Nqo+Ar5jNYNPV-YJQYpLTCf=7oJ1o0VjP-t0nA@mail.gmail.com>
2025-04-01 7:58 ` Sumit Garg [this message]
2025-04-01 8:33 ` [PATCH v6 05/10] tee: implement restricted DMA-heap Jens Wiklander
[not found] < <CAHUa44EGWuVPjoxpG-S66he=6dkvkwzxNewaGKVKXUxrO41ztg@mail.gmail.com>
2025-04-09 12:50 ` Sumit Garg
2025-04-10 6:49 ` Jens Wiklander
[not found] < <CAHUa44FpsCVrbwj1=nsJVJFVJSF1kzKdWAkAMXRu6EdLrLvh8g@mail.gmail.com>
2025-04-08 9:14 ` Sumit Garg
2025-04-08 13:28 ` Jens Wiklander
2025-03-05 13:04 [PATCH v6 00/10] TEE subsystem for restricted dma-buf allocations Jens Wiklander
2025-03-05 13:04 ` [PATCH v6 05/10] tee: implement restricted DMA-heap Jens Wiklander
2025-03-25 6:33 ` Sumit Garg
2025-03-25 10:55 ` Jens Wiklander
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=Z-ucuPzwz4IqVTgb@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=op-tee@lists.trustedfirmware.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