Hello Joakim,
Ok, for delegating cache management to backend.
Regards Manu
-----Original Message----- From: Joakim Bech [mailto:joakim.bech@linaro.org] Sent: lundi 9 mars 2015 13:50 To: Emmanuel MICHEL Cc: tee-dev Subject: Re: [Tee-dev] Interface proposal
Hi Manu,
On Fri, Mar 06, 2015 at 12:45:25PM +0100, Emmanuel MICHEL wrote:
Re,
In example, copy parameters from userland, with cache management.
Do we actually have such a use case? If yes, shouldn't we try to avoid imposing cache management? But I think I'm getting the message that you're trying to tell, i.e, that there are use cases that share functionality, but lives in the gray zone between generic vs specific driver.
If we come to think about such use cases, then I encourage us to bring it up for discussion to decide if it is functionality that could be considered as generic or not. If we decide that it isn't then it has to be something that is handled by the specific driver(s).
So just to hear what others have to say about it, what do you think, is cache management something that is suitable to have in a generic TEE layer?
Regards Manu
-----Original Message----- From: Joakim Bech [mailto:joakim.bech@linaro.org] Sent: vendredi 6 mars 2015 12:40 To: Emmanuel MICHEL Cc: tee-dev Subject: Re: [Tee-dev] Interface proposal
Hi Manu,
On Fri, Mar 06, 2015 at 12:33:41PM +0100, Emmanuel MICHEL wrote:
Hello Joakim,
What is your proposal to deal with the common code with several specific drivers, and can't stand in generic part ?
That is something we have to deal with case by case. Do you have a concrete example that we should consider already know?
Regards Manu
-- Regards, Joakim B
-- Regards, Joakim B