1. 19 Nov, 2017 2 commits
  2. 20 May, 2017 4 commits
  3. 11 May, 2017 1 commit
  4. 27 Apr, 2017 1 commit
  5. 21 Apr, 2017 1 commit
  6. 20 Apr, 2017 2 commits
  7. 19 Apr, 2017 2 commits
  8. 26 Mar, 2017 2 commits
    • Vinayak Chettimada's avatar
      Bluetooth: controller: Fix race waiting for ticker job to complt · a1538a67
      Vinayak Chettimada authored
      
      Same volatile status variable as return and being updated
      in ISR would modify the variable in two context which
      caused the variable to be set to a stale value.
      
      This commit uses two different variables, one for return
      value and the other to be updated by ISR.
      
      Jira: ZEP-1941
      
      Change-id: I19e3bdc85e15bda7891395f3f1f64c2ddbeee0c6
      Signed-off-by: default avatarVinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
      a1538a67
    • Vinayak Chettimada's avatar
      Bluetooth: Controller: Fix assert on role stop/abort · f164b38a
      Vinayak Chettimada authored
      
      Call to ticker_stop/update can fail under the condition
      where in a role is being stopped but at the same time it is
      preempted by the role event that also uses ticker_stop/
      update.
      
      Also if a role closes graceful while it is being stopped,
      the radio ISR will process the stop state with no active
      role at that instance in time. In this case just reset the
      state to none, the role has already been gracefully closed
      before this ISR execution. The above applies to aborting a
      role event too.
      
      This commit adds code to detect these conditions and
      deterministically recover from it.
      
      This commit fixes the assert observed while stopping
      advertiser in the Bluetooth sample scan_adv.
      
      Jira: ZEP-1852
      
      Change-id: I51c8d6e212ef43e3526a199cf7b666a79729c732
      Signed-off-by: default avatarVinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
      f164b38a
  9. 23 Mar, 2017 1 commit
  10. 15 Mar, 2017 1 commit
    • Florian Vaussard's avatar
      kernel: arm: Increase idle stack size to fix corruption by FP_SHARING · dca0e24b
      Florian Vaussard authored
      
      When enabling CONFIG_FP_SHARING on ARM, 64 extra bytes are necessary
      on the stack of each task in order to save FPU registers S16 to S31.
      
      In the case of the idle stack, the default value of 256 bytes is too
      small. As described in ZEP-1470, when the idle task is scheduled out,
      floating point registers are saved, which corrupts the stack frame
      (especially the saved PC value). When scheduling the idle task, the
      restored PC will jump to nowhere, leading to a Usage Fault.
      
      Increase the size of the idle stack by 64 bytes to fix this issue.
      
      JIRA: ZEP-1470
      
      Change-Id: Ib800cd51e5189dda8bf59332db661c21399db3e3
      Signed-off-by: default avatarFlorian Vaussard <florian.vaussard@heig-vd.ch>
      Signed-off-by: default avatarKumar Gala <kumar.gala@linaro.org>
      dca0e24b
  11. 11 Feb, 2017 1 commit
  12. 09 Feb, 2017 1 commit
  13. 08 Feb, 2017 1 commit
  14. 19 Jan, 2017 4 commits
  15. 13 Jan, 2017 2 commits
  16. 12 Jan, 2017 1 commit
  17. 04 Jan, 2017 3 commits
  18. 03 Dec, 2016 4 commits
  19. 02 Dec, 2016 6 commits