Skip to content

Commit 14c73cb

Browse files
committed
Sdtrig: Clarify that all triggers share the same tinfo.version
The purpose of "tinfo.version" field is to describe the version of the whole Sdtrig implementation. Add an explanatory note to make it clearer to spec readers that this means that all triggers will share the same tinfo.version value.
1 parent 22a7576 commit 14c73cb

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

xml/hwbp_registers.xml

+10-3
Original file line numberDiff line numberDiff line change
@@ -177,6 +177,13 @@ same project unless stated otherwise.
177177
<field name="0" bits="XLEN-1:32" access="R" reset="0" />
178178
<field name="version" bits="31:24" access="R" reset="Preset">
179179
Contains the version of the Sdtrig extension implemented.
180+
181+
[NOTE]
182+
====
183+
This field refers to the version of the whole Sdtrig extension.
184+
For that reason, all triggers contain the same version number.
185+
====
186+
180187
<value v="0" name="0">
181188
Supports triggers as described in this spec at commit 5a5c078,
182189
made on February 2, 2023.
@@ -195,9 +202,9 @@ same project unless stated otherwise.
195202
</field>
196203
<field name="0" bits="23:16" access="R" reset="0" />
197204
<field name="info" bits="15:0" access="R" reset="Preset">
198-
One bit for each possible {tdata1-type} enumerated in {csr-tdata1}. Bit N
199-
corresponds to type N. If the bit is set, then that type is
200-
supported by the currently selected trigger.
205+
One bit for each possible {tdata1-type} enumerated in {csr-tdata1}.
206+
Bit N corresponds to type N. If the bit is set, then that type is
207+
supported by the currently selected trigger (by {csr-tselect}).
201208

202209
If the currently selected trigger doesn't exist, this field
203210
contains 1.

0 commit comments

Comments
 (0)