docs: vendor-ibm-astlpc: Fix packet exchange order of operations
We read data from the KCS channels to confirm the command type before
reading the packet data from the FW window.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I19378b20c91183b5403f046cb7ab22d83c257e40
diff --git a/docs/bindings/vendor-ibm-astlpc.md b/docs/bindings/vendor-ibm-astlpc.md
index b311799..0618000 100644
--- a/docs/bindings/vendor-ibm-astlpc.md
+++ b/docs/bindings/vendor-ibm-astlpc.md
@@ -115,8 +115,9 @@
1. Read from the KCS status register, which shows that the single-byte KCS data
buffer is full
-2. Read the MCTP packet from the LPC FW window
-3. Read from the KCS buffer, to clear the 'buffer full' state.
+2. Read the provided command from the KCS data buffer, acknowledging the
+ interrupt
+3. Read the MCTP packet from the LPC FW window
### Scope