SHIVAM DEOLANKAR commented on a discussion on testsuites/validation/tc-intr-set-priority.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_151414 > } > > sc = rtems_interrupt_set_priority( vector, priority ); > + > + /* > + * Some BSPs support full uint32_t priority range > + * UINT32_MAX may be valid. > + */ > + if ( !ctx->valid_priority && sc == RTEMS_SUCCESSFUL ){ For the RISC-V implementation, `bsp_interrupt_set_priority()` does not perform any priority range validation.Which means it accepts full uint32_t range and always return RTEMS_SUCCESSFUL for external interrupts, so UINT32_MAX is valid. One approach would be to skip `Invalid Priority -> RTEMS_INVALID_PRIORITY `validation case for BSPs where no invalid interrupt priority exists. Would that be correct from your pov? -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_151414 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
