[RTEMS Project] #4737: rtems_interrupt_is_pending behaviour expected between tc-intr-clear and tc-intr-raise-on

[RTEMS trac]

#4737: rtems_interrupt_is_pending behaviour expected between tc-intr-clear and tc-
intr-raise-on
-----------------------------------+--------------------
  Reporter:  Lucian-Raul Silistru  |      Owner:  joel@…
      Type:  defect                |     Status:  new
  Priority:  normal                |  Milestone:
 Component:  test                  |    Version:  6
  Severity:  normal                |   Keywords:
Blocked By:                        |   Blocking:
-----------------------------------+--------------------
 In testsuite tc-validation-intr there's a discrepancy between expected
 behaviour of rtems_interrupt_is_pending when the vector is disabled in tc-
 intr-clear and tc-intr-raise-on.

 In tc-intr-raise-on CheckRaiseOn IsPending is ignored with a comment that
 not all interrupt controller will signal a pending interrupt when the
 vector is disabled.

 In tc-intr-clear CheckClear there's a verification under
 if ( attr->can_disable )
 that fails the test if IsPending does not return true after an interrupt
 is raised on a disabled vector.

 According to the tc-intr-raise-on comment, the tc-intr-clear check should
 be relaxed, is that correct?

--
Ticket URL: <http://devel.rtems.org/ticket/4737>
RTEMS Project <http://www.rtems.org/>
RTEMS Project