From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, Ross.Burton@arm.com,
Jon.Mason@arm.com, emekcan.aras@arm.com
Cc: nd@arm.com
Subject: Re: [PATCH 0/1] arm-bsp/corstone1000: fix synchronization issue on openamp notification
Date: Thu, 23 Nov 2023 11:24:34 -0500 [thread overview]
Message-ID: <170075667406.1682259.2599155461322562962.b4-ty@arm.com> (raw)
In-Reply-To: <20231120153738.2732021-1-emekcan.aras@arm.com>
On Mon, 20 Nov 2023 15:37:37 +0000, emekcan.aras@arm.com wrote:
> From: Emekcan Aras <emekcan.aras@arm.com>
>
> This fixes a race that is observed rarely in the FVP. It occurs in FVP
> when tfm sends the notication ack in openamp, and then reset the access
> request which resets the mhu registers before received by the host
> processor. It implements the fix both in SE and the host processor openamp
> wrapper. This solution enables polling on the status register of mhu until
> the notificaiton is read by the host processor. (Inspired by
> signal_and_wait_for_signal function in mhu_wrapper_v2_x.c in trusted-firmware-m
> https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/ext/target/arm/rss/common/native_drivers/mhu_wrapper_v2_x.c#n61)
>
> [...]
Applied, thanks!
[1/1] arm-bsp/corstone1000: fix synchronization issue on openamp notification
commit: 63bb9a306e82149ec6abbe9771e731991130738c
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2023-11-23 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 15:37 [PATCH 0/1] arm-bsp/corstone1000: fix synchronization issue on openamp notification emekcan.aras
2023-11-20 15:37 ` [PATCH 1/1] " emekcan.aras
2023-11-23 16:24 ` Jon Mason [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=170075667406.1682259.2599155461322562962.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=Jon.Mason@arm.com \
--cc=Ross.Burton@arm.com \
--cc=emekcan.aras@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).