Merge tag 'docs-5.17-2' of git://git.lwn.net/linux

Pull documentation fixes from Jonathan Corbet:
 "Three small documentation fixes"

* tag 'docs-5.17-2' of git://git.lwn.net/linux:
  Documentation: fix firewire.rst ABI file path error
  docs: ftrace: fix ambiguous sentence
  docs: staging/tee.rst: fix two typos found while reading

diff --combined Documentation/staging/tee.rst
index 3c63d8dcd61eb7b4ed65e202087e7dfb0812b711,4eec213eaefe286e22a13571c14699c0d0aa74a8..498343c7ab088e8ed6b981ead561dd94f39fbff6
--- 1/Documentation/staging/tee.rst
--- 2/Documentation/staging/tee.rst
+++ b/Documentation/staging/tee.rst
@@@ -184,36 -184,6 +184,36 @@@ order to support device enumeration. I
  application to retrieve a list of Trusted Applications which can be registered
  as devices on the TEE bus.
  
 +OP-TEE notifications
 +--------------------
 +
 +There are two kinds of notifications that secure world can use to make
 +normal world aware of some event.
 +
 +1. Synchronous notifications delivered with ``OPTEE_RPC_CMD_NOTIFICATION``
 +   using the ``OPTEE_RPC_NOTIFICATION_SEND`` parameter.
 +2. Asynchronous notifications delivered with a combination of a non-secure
 +   edge-triggered interrupt and a fast call from the non-secure interrupt
 +   handler.
 +
 +Synchronous notifications are limited by depending on RPC for delivery,
 +this is only usable when secure world is entered with a yielding call via
 +``OPTEE_SMC_CALL_WITH_ARG``. This excludes such notifications from secure
 +world interrupt handlers.
 +
 +An asynchronous notification is delivered via a non-secure edge-triggered
 +interrupt to an interrupt handler registered in the OP-TEE driver. The
 +actual notification value are retrieved with the fast call
 +``OPTEE_SMC_GET_ASYNC_NOTIF_VALUE``. Note that one interrupt can represent
 +multiple notifications.
 +
 +One notification value ``OPTEE_SMC_ASYNC_NOTIF_VALUE_DO_BOTTOM_HALF`` has a
 +special meaning. When this value is received it means that normal world is
 +supposed to make a yielding call ``OPTEE_MSG_CMD_DO_BOTTOM_HALF``. This
 +call is done from the thread assisting the interrupt handler. This is a
 +building block for OP-TEE OS in secure world to implement the top half and
 +bottom half style of device drivers.
 +
  AMD-TEE driver
  ==============
  
@@@ -255,7 -225,7 +255,7 @@@ The following picture shows a high leve
   +--------------------------+      +---------+--------------------+
  
  At the lowest level (in x86), the AMD Secure Processor (ASP) driver uses the
- CPU to PSP mailbox regsister to submit commands to the PSP. The format of the
+ CPU to PSP mailbox register to submit commands to the PSP. The format of the
  command buffer is opaque to the ASP driver. It's role is to submit commands to
  the secure processor and return results to AMD-TEE driver. The interface
  between AMD-TEE driver and AMD Secure Processor driver can be found in [6].
@@@ -290,7 -260,7 +290,7 @@@ cancel_req driver callback is not suppo
  
  The GlobalPlatform TEE Client API [5] can be used by the user space (client) to
  talk to AMD's TEE. AMD's TEE provides a secure environment for loading, opening
- a session, invoking commands and clossing session with TA.
+ a session, invoking commands and closing session with TA.
  
  References
  ==========