Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify WARL description for dmode=0 and action=1. #1009

Merged
merged 1 commit into from
May 15, 2024
Merged

Conversation

rtwfroody
Copy link
Collaborator

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 Outdated
Comment on lines 60 to 62
This action is only legal when the trigger's {mcontrol-dmode} is 1. Since the
{csr-tdata1} is WARL, hardware must prevent it from containing {tdata1-dmode}=0
and action=1. +
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This action is only legal when the trigger's {mcontrol-dmode} is 1. Since the
{csr-tdata1} is WARL, hardware must prevent it from containing {tdata1-dmode}=0
and action=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. +

Or "the tdata1 register" would also be OK.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. Thanks.

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.
@rtwfroody
Copy link
Collaborator Author

This introduces a new "must", but that is OK because it's simply restating something about a field that is only legal in certain cases.

@rtwfroody rtwfroody merged commit 28aa582 into main May 15, 2024
1 check passed
@rtwfroody rtwfroody deleted the action_warl branch May 15, 2024 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants