Skip to content

Commit

Permalink
Fix "A RPMI" to "An RMPI"
Browse files Browse the repository at this point in the history
The correct form is "An RPMI" because the abbreviation "RPMI" begins
with a vowel sound ('ar').

Signed-off-by: Ley Foon Tan <[email protected]>
  • Loading branch information
Ley Foon Tan committed Mar 4, 2024
1 parent f484903 commit 964a6c6
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 7 deletions.
4 changes: 2 additions & 2 deletions src/message-protocol.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ acknowledgment must follow byte ordering defined by the RPMI transport.

==== Message Header
Message header has a fixed size of `12-byte` which further contains three
fields each of `4-byte`. Each message gets a unique identity in a RPMI instance
fields each of `4-byte`. Each message gets a unique identity in an RPMI instance
through its header.

Both REQUEST and ACKNOWLEDGEMENT messages have the same message format.
Expand All @@ -66,7 +66,7 @@ image::message-format.png[700,900]
|===
| Word | Name | Description
| 0 | *TOKEN* | Message identifier. Unique to each
request - acknowledgement transaction for a RPMI implementation instance.
request - acknowledgement transaction for an RPMI implementation instance.
In case of Notifications, `SERVICE_ID` and `MESSAGE_TYPE` for notification
messages are fixed which will contribute to the unique identity of the message
in that RPMI instance implementation.
Expand Down
2 changes: 1 addition & 1 deletion src/srvgrp-base.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ Get version of the implemented RPMI specification
|===

==== Service: *GET_HW_INFO*
This service is used to retrieve the Vendor ID and Name of the Vendor having a
This service is used to retrieve the Vendor ID and Name of the Vendor having an
RPMI implementation on PuC. Each vendor will be assigned a unique Vendor ID.
[#table_base_gethwinfo_request_data]
.Request Data
Expand Down
8 changes: 4 additions & 4 deletions src/transport.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,15 @@ RPMI Transport is the abstraction over a physical medium used to send and
receive messages between an Application Processor and Platform Microcontroller
enabling bidirectional communication.

A RPMI transport instance provides a bidirectional communication channel between
An RPMI transport instance provides a bidirectional communication channel between
a privilege level of a set of APs and one PuC. There can be multiple RPMI
transport instances between a set of APs and one PuC. For example: there can
be a separate transport instance between each privilege level of APs and one
PuC. A platform can also have multiple PuCs with each having its own set of
RPMI transport to communicate with the APs. The _Figure 1.2_ above shows different
topologies of RPMI transport.

The physical medium of a RPMI transport can be shared memory or I2C or SPI or
The physical medium of an RPMI transport can be shared memory or I2C or SPI or
some other medium. This specification only defines a shared memory based RPMI
transport but a platform can define its own RPMI transport.

Expand All @@ -26,9 +26,9 @@ the Platform Microcontroller or vice versa.
image::transport-bidirectional.png[400,400]

=== Doorbell Interrupt
A RPMI transport may also provide doorbell interrupts to either Application
An RPMI transport may also provide doorbell interrupts to either Application
Processors or Platform Microcontrollers or both to signal new messages.
The doorbell mechanism is optional for a RPMI transport and implementations can
The doorbell mechanism is optional for an RPMI transport and implementations can
always use a polling mechanism for checking the arrival of messages.

The doorbell interrupt from the APs to the PuC can be a MSI or a wired interrupt with a
Expand Down

0 comments on commit 964a6c6

Please sign in to comment.