Central | IRQ maximum priority is poorly specified/tested (#17)

[Gedare Bloom (@gedare)]

Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/17



## Summary
<!--
Please provide as much information as possible such as error messages or attaching logs
-->

We have `spec/rtems/intr/if/attributes.yml` that defines `maximum_priority` as not 0 and of type uint32. it is therefore implied that the maximum priority is `UINT32_MAX`. But what appears in tests is the use of `priority = UINT32_MAX` as an invalid priority.

This causes a problem for example in riscv where UINT32_MAX is an allowed priority value, while 0 is not allowed.

The definition of maximum_priority also implicitly defines a minimum priority of 0, but again this is not supportable by all hardware targets so I don't think this is a good requirement.

## Steps to reproduce


<!-- Pre-set options
- milestone
-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/17
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260515/75cdfbf4/attachment.htm>