RF driver -- .conflictHook is not invoked when multiple TRIG_NOW commands in pendQ

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • TI Device Drivers
    • TIDRIVERS-3391
    • 3.80.00
    • CORESDK_4_10_00
    • Hide
      During implementation of TI154STACK-2325 it was seen that the .conflictHook was not called in time to handle a conflict for a TRIG_ABSTIME command when there are multiple TRIG_NOW commands before it in the pendQ.

      Suggested fix is to make the timeout for the conflict timer walk the pendQ until it reaches a TRIG_ABSTIME command
      Show
      During implementation of TI154STACK-2325 it was seen that the .conflictHook was not called in time to handle a conflict for a TRIG_ABSTIME command when there are multiple TRIG_NOW commands before it in the pendQ. Suggested fix is to make the timeout for the conflict timer walk the pendQ until it reaches a TRIG_ABSTIME command

      RF driver – .conflictHook is not invoked when multiple TRIG_NOW commands in pendQ

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-1785 - RF driver -- .conflictHook is not i...
                SYNCHRONIZED
                • Last Sync Date: