docs: gPTP add sequence diagram links

1 files changed, 15 insertions, 0 deletions

diff --git a/documents/design/AVnu_gPTP_Code.asciidoc b/documents/design/AVnu_gPTP_Code.asciidoc
index b3547329..f823a720 100644
--- a/documents/design/AVnu_gPTP_Code.asciidoc
+++ b/documents/design/AVnu_gPTP_Code.asciidoc
@@ -1,6 +1,8 @@
 = AVnu gPTP Code
 :toc:
 :toc-placement!:
+:repo: https://github.com/andrew-elder/Open-AVB/blob
+:img: {repo}/gh-pages/images/ptp
 
 toc::[]
 
@@ -213,6 +215,9 @@ initialized and transmitted. The transmit timestamp is read from the
 timestamper object. A PTPMessageFollowUp object is initialized and the
 timestamp is added to the object and transmitted.
 
+image:{img}/Sync%20Transmission%20%28PTP_MASTER%20mode%29.PNG[]
+*Figure 1. Sync Transmission (PTP_MASTER mode) Sequence Diagram*
+
 [[sync-reception-ptp_slave-mode]]
 ==== Sync Reception (PTP_SLAVE mode)
 
@@ -228,6 +233,9 @@ IEEE1588Clock::setMasterOffset. Reception of a valid sync and followup
 restarts the SYNC_RECEIPT_TIMEOUT timer on the corresponding port
 object.
 
+image:{img}/Sync%20Reception%20%28PTP_SLAVE%20mode%29.PNG[]
+*Figure 2. Sync Reception (PTP_SLAVE mode) Sequence Diagram*
+
 [[pdelay-transmission]]
 ==== Pdelay Transmission
 
@@ -246,6 +254,10 @@ is calculated:
 
 The link delay in the Sync Reception operation.
 
+image:{img}/Pdelay%20Transmission.PNG[]
+*Figure 3. PDelay Transmission Sequence Diagram*
+
+
 [[pdelay-reception]]
 ==== PDelay Reception
 
@@ -255,6 +267,9 @@ receive timestamp, and transmitted. A response followup
 (PTPMessagePathDelayRespFollowUp) is initialized, populated with the
 response transmit timestamp, and transmitted.
 
+image:{img}/Pdelay%20Reception.PNG[]
+*Figure 4. PDelay Reception Sequence Diagram*
+
 [[os-abstractions]]
 === OS Abstractions