Re: [PATCH 00/10] Trusted Execution Environment (TEE) driver for Qualcomm TEE (QTEE)

[Amirreza Zarrabi <quic_azarrabi@quicinc.com>]

On 12/4/2024 10:43 AM, Dmitry Baryshkov wrote:
> On Wed, Dec 04, 2024 at 09:13:43AM +1100, Amirreza Zarrabi wrote:
>> Based on our discussions, we implemented significant changes. We essentially
>> rewrote most of the files and altered the overall direction, except for a
>> couple of files. The changelog entry would have been extensive.
> 
> At least some changelog should be provided, even if tells "reworked to
> use TEE framework, made it jump over the head and tie the shoelaces".
> 

Sure, I'll provide some changelog.

> Also please don't top-post, this style is frowned upon in the mailing
> list discussions, it breaks the logic of reading.
> 

;) Oops, that shouldn't have been sent out like this. My apologies.
I'll ensure it doesn't happen again..

- Amir

>>
>> - Amir
>>
>> On 12/3/2024 5:06 PM, Trilok Soni wrote:
>>> On 12/2/2024 8:19 PM, Amirreza Zarrabi wrote:
>>>> This patch series introduces a Trusted Execution Environment (TEE)
>>>> driver for Qualcomm TEE (QTEE). QTEE enables Trusted Applications (TAs)
>>>> and services to run securely. It uses an object-based interface, where
>>>> each service is an object with sets of operations. Clients can invoke
>>>> these operations on objects, which can generate results, including other
>>>> objects. For example, an object can load a TA and return another object
>>>> that represents the loaded TA, allowing access to its services.
>>>
>>> The first patch series was RFC and now you had removed the RFC. Can you please
>>> provide the reasons?
>>>
>>> https://lwn.net/ml/all/20240702-qcom-tee-object-and-ioctls-v1-0-633c3ddf57ee@quicinc.com/
>>>
>>> I understand that you have now changed to tee framework but I want to check
>>> if we should continue with the version and increment here or start from [00]?
>>>
>