From 68a7eb816e5c7ca0e7115c945ccb6c66590e8982 Mon Sep 17 00:00:00 2001
From: Tim Newsome <tim@casualhacker.net>
Date: Wed, 24 Apr 2024 09:19:41 -0700
Subject: [PATCH] Simplify WARL description for dmode=0 and action=1.

Instead of describing a recommended implementation (which didn't cover
all cases), explicitly state the value that is illegal and let hardware
choose how to do that.

Addresses #995.
---
 Sdtrig.adoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Sdtrig.adoc b/Sdtrig.adoc
index 6fe91cd7..06cac4bc 100644
--- a/Sdtrig.adoc
+++ b/Sdtrig.adoc
@@ -57,7 +57,9 @@ Triggers can be configured to take one of several actions when they fire. <<tab:
 ^| Value | Description
 |0 | Raise a breakpoint exception. (Used when software wants to use the trigger module without an external debugger attached.) `xepc` must contain the virtual address of the next instruction that must be executed to preserve the program flow.
 |1 | Enter Debug Mode. {csr-dpc} must contain the virtual address of the next instruction that must be executed to preserve the program flow. +
-This action is only legal when the trigger's {mcontrol-dmode} is 1. Since the `tdata` registers are *WARL*, hardware should clear the action field whenever the action field is 1, the new value of {mcontrol-dmode} would be 0, and the new value of  he action field would be 1. +
+This action is only legal when the trigger's {mcontrol-dmode} is 1.  Since
+{csr-tdata1} is WARL, hardware must prevent it from containing {tdata1-dmode}=0
+and action=1. +
 This action can only be supported if `Sdext` is implemented on the hart.
 | 2 | Trace on, described in the trace specification. 
 | 3 | Trace off, described in the trace specification.