summaryrefslogtreecommitdiffstats
path: root/drivers/firmware/ti_sci.h
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@arm.com>2019-07-08 16:48:36 +0200
committerSudeep Holla <sudeep.holla@arm.com>2019-08-12 13:22:59 +0200
commit9dc34d635c67e57051853855c43249408641a5ab (patch)
treeed835ee597152d61b9cdfa92ab044910cf257df6 /drivers/firmware/ti_sci.h
parentfirmware: arm_scmi: Use the term 'message' instead of 'command' (diff)
downloadlinux-9dc34d635c67e57051853855c43249408641a5ab.tar.xz
linux-9dc34d635c67e57051853855c43249408641a5ab.zip
firmware: arm_scmi: Check if platform has released shmem before using
Sometimes platfom may take too long to respond to the command and OS might timeout before platform transfer the ownership of the shared memory region to the OS with the response. Since the mailbox channel associated with the channel is freed and new commands are dispatch on the same channel, OS needs to wait until it gets back the ownership. If not, either OS may end up overwriting the platform response for the last command(which is fine as OS timed out that command) or platform might overwrite the payload for the next command with the response for the old. The latter is problematic as platform may end up interpretting the response as the payload. In order to avoid such race, let's wait until the OS gets back the ownership before we prepare the shared memory with the payload for the next command. Reported-by: Jim Quinlan <james.quinlan@broadcom.com> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Diffstat (limited to 'drivers/firmware/ti_sci.h')
0 files changed, 0 insertions, 0 deletions