From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/chrome: cros_ec_rpmsg: Fix race with host event.
Date: Tue, 3 Mar 2020 11:03:21 +0100 [thread overview]
Message-ID: <b8de9c57-8eae-f1a7-ae25-728f0dd16176@collabora.com> (raw)
In-Reply-To: <20200214082638.92070-1-pihsun@chromium.org>
Hi Pi-Hsun,
On 14/2/20 9:26, Pi-Hsun Shih wrote:
> Host event can be sent by remoteproc by any time, and
> cros_ec_rpmsg_callback would be called after cros_ec_rpmsg_create_ept.
> But the cros_ec_device is initialized after that, which cause host event
> handler to use cros_ec_device that are not initialized properly yet.
>
> Fix this by don't schedule host event handler before cros_ec_register
> returns. Instead, remember that we have a pending host event, and
> schedule host event handler after cros_ec_register.
>
> Fixes: 71cddb7097e2 ("platform/chrome: cros_ec_rpmsg: Fix race with host command when probe failed.")
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
> ---
Applied for 5.7
> drivers/platform/chrome/cros_ec_rpmsg.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/chrome/cros_ec_rpmsg.c b/drivers/platform/chrome/cros_ec_rpmsg.c
> index dbc3f5523b83..7e8629e3db74 100644
> --- a/drivers/platform/chrome/cros_ec_rpmsg.c
> +++ b/drivers/platform/chrome/cros_ec_rpmsg.c
> @@ -44,6 +44,8 @@ struct cros_ec_rpmsg {
> struct completion xfer_ack;
> struct work_struct host_event_work;
> struct rpmsg_endpoint *ept;
> + bool has_pending_host_event;
> + bool probe_done;
> };
>
> /**
> @@ -177,7 +179,14 @@ static int cros_ec_rpmsg_callback(struct rpmsg_device *rpdev, void *data,
> memcpy(ec_dev->din, resp->data, len);
> complete(&ec_rpmsg->xfer_ack);
> } else if (resp->type == HOST_EVENT_MARK) {
> - schedule_work(&ec_rpmsg->host_event_work);
> + /*
> + * If the host event is sent before cros_ec_register is
> + * finished, queue the host event.
> + */
> + if (ec_rpmsg->probe_done)
> + schedule_work(&ec_rpmsg->host_event_work);
> + else
> + ec_rpmsg->has_pending_host_event = true;
> } else {
> dev_warn(ec_dev->dev, "rpmsg received invalid type = %d",
> resp->type);
> @@ -240,6 +249,11 @@ static int cros_ec_rpmsg_probe(struct rpmsg_device *rpdev)
> return ret;
> }
>
> + ec_rpmsg->probe_done = true;
> +
> + if (ec_rpmsg->has_pending_host_event)
> + schedule_work(&ec_rpmsg->host_event_work);
> +
> return 0;
> }
>
>
> base-commit: b19e8c68470385dd2c5440876591fddb02c8c402
>
prev parent reply other threads:[~2020-03-03 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 8:26 Pi-Hsun Shih
2020-02-14 15:10 ` Enric Balletbo i Serra
2020-02-15 3:56 ` Pi-Hsun Shih
2020-02-17 15:55 ` Enric Balletbo i Serra
2020-02-28 8:52 ` Enric Balletbo i Serra
2020-03-02 5:59 ` Pi-Hsun Shih
2020-03-03 10:03 ` Enric Balletbo i Serra [this message]
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=b8de9c57-8eae-f1a7-ae25-728f0dd16176@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pihsun@chromium.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®