From: Balint Dobszay <balint.dobszay@arm.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: op-tee@lists.trustedfirmware.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jens.wiklander@linaro.org,
corbet@lwn.net, sudeep.holla@arm.com, rdunlap@infradead.org,
krzk@kernel.org, gyorgy.szing@arm.com
Subject: Re: [PATCH v2 1/3] tee: optee: Move pool_op helper functions
Date: Tue, 05 Mar 2024 11:21:40 +0100 [thread overview]
Message-ID: <ABE8D9AB-8F66-49F4-B442-F74EC2EF5C04@arm.com> (raw)
In-Reply-To: <CAFA6WYMocdcQXaqk8hS8dwnfwJLNWKWSEfMLO4wXyCQM=TQ8vQ@mail.gmail.com>
On 5 Mar 2024, at 6:36, Sumit Garg wrote:
> On Mon, 4 Mar 2024 at 19:57, Balint Dobszay <balint.dobszay@arm.com> wrote:
>>
>> On 4 Mar 2024, at 10:17, Sumit Garg wrote:
>>
>>> Hi Balint,
>>>
>>> On Mon, 4 Mar 2024 at 14:33, Balint Dobszay <balint.dobszay@arm.com> wrote:
>>>>
>>>> Hi Sumit,
>>>>
>>>
>>> [snip]
>>>
>>>>>> diff --git a/include/linux/tee_drv.h b/include/linux/tee_drv.h
>>>>>> index 911ddf92dcee..4cf402424e71 100644
>>>>>> --- a/include/linux/tee_drv.h
>>>>>> +++ b/include/linux/tee_drv.h
>>>>>> @@ -275,6 +275,17 @@ void *tee_get_drvdata(struct tee_device *teedev);
>>>>>> struct tee_shm *tee_shm_alloc_priv_buf(struct tee_context *ctx, size_t size);
>>>>>> struct tee_shm *tee_shm_alloc_kernel_buf(struct tee_context *ctx, size_t size);
>>>>>>
>>>>>> +int tee_shm_pool_op_alloc_helper(struct tee_shm_pool *pool, struct tee_shm *shm,
>>>>>> + size_t size, size_t align,
>>>>>> + int (*shm_register)(struct tee_context *ctx,
>>>>>> + struct tee_shm *shm,
>>>>>> + struct page **pages,
>>>>>> + size_t num_pages,
>>>>>> + unsigned long start));
>>>>>> +void tee_shm_pool_op_free_helper(struct tee_shm_pool *pool, struct tee_shm *shm,
>>>>>> + int (*shm_unregister)(struct tee_context *ctx,
>>>>>> + struct tee_shm *shm));
>>>>>> +
>>>>>
>>>>> These rather belong to drivers/tee/tee_private.h as we shouldn't
>>>>> expose them to other kernel client drivers.
>>>>
>>>> As per the discussion in the other thread I'll ignore this.
>>>>
>>>
>>> Then it will have conflicts with this [1] patch. If you are fine to
>>> incorporate [1] in your series then the right place for these function
>>> declarations should be include/linux/tee_core.h.
>>>
>>> [1] https://www.spinics.net/lists/kernel/msg5122983.html
>>
>> You're right, I'll rebase my patches on this.
>>
>> By incorporating your patch in my series, do you mean that I should just
>> add it as the first patch in the series for the next version?
>
> If you are happy to carry it then I would be in favour of this to take
> care of dependency.
Sure, I've added it to v3.
Regards,
Balint
>> Or keep my
>> series as is (do the rebase of course) and just mention that it's using
>> your patch as base?
>>
>> Regards,
>> Balint
>>
>>>>
>>>>>> struct tee_shm *tee_shm_register_kernel_buf(struct tee_context *ctx,
>>>>>> void *addr, size_t length);
>>>>>>
>>>>>> --
>>>>>> 2.34.1
>>>>>>
next prev parent reply other threads:[~2024-03-05 10:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 9:51 [PATCH v2 0/3] TEE driver for Trusted Services Balint Dobszay
2024-02-23 9:51 ` [PATCH v2 1/3] tee: optee: Move pool_op helper functions Balint Dobszay
2024-02-27 6:06 ` Sumit Garg
2024-02-27 15:49 ` Jens Wiklander
2024-02-28 5:58 ` Sumit Garg
2024-02-28 8:40 ` Jens Wiklander
2024-02-28 11:20 ` Sumit Garg
2024-02-28 11:48 ` Jens Wiklander
2024-03-04 9:03 ` Balint Dobszay
2024-03-04 9:17 ` Sumit Garg
2024-03-04 14:26 ` Balint Dobszay
2024-03-05 5:36 ` Sumit Garg
2024-03-05 10:21 ` Balint Dobszay [this message]
2024-02-23 9:51 ` [PATCH v2 2/3] tee: tstee: Add Trusted Services TEE driver Balint Dobszay
2024-02-27 7:08 ` Sumit Garg
2024-03-04 9:04 ` Balint Dobszay
2024-02-23 9:51 ` [PATCH v2 3/3] Documentation: tee: Add TS-TEE driver Balint Dobszay
2024-02-27 7:14 ` Sumit Garg
2024-03-04 9:05 ` Balint Dobszay
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=ABE8D9AB-8F66-49F4-B442-F74EC2EF5C04@arm.com \
--to=balint.dobszay@arm.com \
--cc=corbet@lwn.net \
--cc=gyorgy.szing@arm.com \
--cc=jens.wiklander@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=rdunlap@infradead.org \
--cc=sudeep.holla@arm.com \
--cc=sumit.garg@linaro.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
all inboxes | Powered by JetHome®