From: "Gavin Liu (劉哲廷)" <Gavin.Liu@mediatek.com>
To: "jerome.forissier@linaro.org" <jerome.forissier@linaro.org>,
"jens.wiklander@linaro.org" <jens.wiklander@linaro.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"sumit.garg@linaro.org" <sumit.garg@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"op-tee@lists.trustedfirmware.org"
<op-tee@lists.trustedfirmware.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH] optee: support wq_sleep_timeout
Date: Mon, 29 Jan 2024 02:32:46 +0000 [thread overview]
Message-ID: <0e9e3ec2079c1a9ac49ea1b93370a48b8e4a78cc.camel@mediatek.com> (raw)
In-Reply-To: <d33bad27-da65-4866-96e7-a249824fcb6e@linaro.org>
Hi Jerome,
Thanks very much for the reviewing.
On Thu, 2024-01-25 at 10:46 +0100, Jerome Forissier wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> On 1/25/24 06:27, gavin.liu via OP-TEE wrote:
> > From: Gavin Liu <gavin.liu@mediatek.com>
> >
> > Add wq_sleep_timeout to support self waking when timeout for secure
> > driver usage.
> >
> > Signed-off-by: Gavin Liu <gavin.liu@mediatek.com>
> > ---
> > drivers/tee/optee/notif.c | 9 +++++++--
> > drivers/tee/optee/optee_private.h | 2 +-
> > drivers/tee/optee/rpc.c | 10 ++++++++--
> > 3 files changed, 16 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/tee/optee/notif.c b/drivers/tee/optee/notif.c
> > index 05212842b0a5..d5e5c0645609 100644
> > --- a/drivers/tee/optee/notif.c
> > +++ b/drivers/tee/optee/notif.c
> > @@ -29,7 +29,7 @@ static bool have_key(struct optee *optee, u_int
> key)
> > return false;
> > }
> >
> > -int optee_notif_wait(struct optee *optee, u_int key)
> > +int optee_notif_wait(struct optee *optee, u_int key, u32 timeout)
> > {
> > unsigned long flags;
> > struct notif_entry *entry;
> > @@ -70,7 +70,12 @@ int optee_notif_wait(struct optee *optee, u_int
> key)
> > * Unlock temporarily and wait for completion.
> > */
> > spin_unlock_irqrestore(&optee->notif.lock, flags);
> > -wait_for_completion(&entry->c);
> > +if (timeout != 0) {
> > +if (!wait_for_completion_timeout(&entry->c, timeout))
> > +rc = -ETIMEDOUT;
> > +} else {
> > +wait_for_completion(&entry->c);
> > +}
> > spin_lock_irqsave(&optee->notif.lock, flags);
> >
> > list_del(&entry->link);
> > diff --git a/drivers/tee/optee/optee_private.h
> b/drivers/tee/optee/optee_private.h
> > index 7a5243c78b55..da990c4016ec 100644
> > --- a/drivers/tee/optee/optee_private.h
> > +++ b/drivers/tee/optee/optee_private.h
> > @@ -252,7 +252,7 @@ struct optee_call_ctx {
> >
> > int optee_notif_init(struct optee *optee, u_int max_key);
> > void optee_notif_uninit(struct optee *optee);
> > -int optee_notif_wait(struct optee *optee, u_int key);
> > +int optee_notif_wait(struct optee *optee, u_int key, u32 timeout);
> > int optee_notif_send(struct optee *optee, u_int key);
> >
> > u32 optee_supp_thrd_req(struct tee_context *ctx, u32 func, size_t
> num_params,
> > diff --git a/drivers/tee/optee/rpc.c b/drivers/tee/optee/rpc.c
> > index e69bc6380683..14e6246aaf05 100644
> > --- a/drivers/tee/optee/rpc.c
> > +++ b/drivers/tee/optee/rpc.c
> > @@ -130,6 +130,8 @@ static void
> handle_rpc_func_cmd_i2c_transfer(struct tee_context *ctx,
> > static void handle_rpc_func_cmd_wq(struct optee *optee,
> > struct optee_msg_arg *arg)
> > {
> > +int rc = 0;
> > +
> > if (arg->num_params != 1)
> > goto bad;
> >
> > @@ -139,7 +141,8 @@ static void handle_rpc_func_cmd_wq(struct optee
> *optee,
> >
> > switch (arg->params[0].u.value.a) {
> > case OPTEE_RPC_NOTIFICATION_WAIT:
> > -if (optee_notif_wait(optee, arg->params[0].u.value.b))
> > +rc = optee_notif_wait(optee, arg->params[0].u.value.b, arg-
> >params[0].u.value.c);
>
> optee/optee_rpc_cmd.h needs updating (near "Waiting on notification")
> to reflect the meaning
> of value.c.
>
Ok, I will update the patch for this.
> Was value.c required to be zero prior to this change? Otherwise this
> could lead to undefined
> behavior.
>
>
This value comes from optee-os, and it is zero by default now.
> > +if (rc)
> > goto bad;
> > break;
> > case OPTEE_RPC_NOTIFICATION_SEND:
> > @@ -153,7 +156,10 @@ static void handle_rpc_func_cmd_wq(struct
> optee *optee,
> > arg->ret = TEEC_SUCCESS;
> > return;
> > bad:
> > -arg->ret = TEEC_ERROR_BAD_PARAMETERS;
> > +if (rc == -ETIMEDOUT)
> > +arg->ret = TEEC_ERROR_BUSY;
> > +else
> > +arg->ret = TEEC_ERROR_BAD_PARAMETERS;
> > }
> >
> > static void handle_rpc_func_cmd_wait(struct optee_msg_arg *arg)
>
> --
> Jerome
next prev parent reply other threads:[~2024-01-29 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 5:27 [PATCH] optee: support wq_sleep_timeout gavin.liu
2024-01-25 9:46 ` Jerome Forissier
2024-01-29 2:32 ` Gavin Liu (劉哲廷) [this message]
2024-01-25 15:02 ` Jens Wiklander
2024-01-29 2:17 ` Gavin Liu (劉哲廷)
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=0e9e3ec2079c1a9ac49ea1b93370a48b8e4a78cc.camel@mediatek.com \
--to=gavin.liu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jens.wiklander@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=op-tee@lists.trustedfirmware.org \
--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