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

Clarify behaviour of xnxti register version in smclicshv #402

Open
jakubahh opened this issue Aug 27, 2024 · 1 comment
Open

Clarify behaviour of xnxti register version in smclicshv #402

jakubahh opened this issue Aug 27, 2024 · 1 comment
Assignees
Labels
v1.0 resolve for 1.0

Comments

@jakubahh
Copy link

The section "smclicshv Changes to Next Interrupt Handler Address and Interrupt-Enable
CSRs (xnxti)" modifies the behaviour of immediate version of xnxti, but doesn't clearly state how register version should behave

Now there are multiple possible interpretations of the xnxti register version's behaviour.
1, The register version behaves as defined in " Next Interrupt Handler Address and Interrupt-Enable CSRs (xnxti)"
2, The register version behaves the same as immediate version
3, The register version contains the original difference in clic.level comparison (clic.level > rs1[23:16]) while returning zero when the incoming interrupt is hardware vectored.

The option 3, seems to be the intended one.
Can the difference between register and immediate version get clear definition in smclicshv?

@jb-brelot-nxp jb-brelot-nxp added the v1.0 resolve for 1.0 label Oct 7, 2024
@jb-brelot-nxp jb-brelot-nxp self-assigned this Oct 7, 2024
@jb-brelot-nxp
Copy link
Collaborator

maybe related to #415

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.0 resolve for 1.0
Projects
None yet
Development

No branches or pull requests

2 participants