| Age | Commit message (Collapse) | Author | 
|---|
|  | * Avoid deadlocks by using a deadicated workqueue for sending
  position state notifications from peripherals. | 
|  | * Zephyr BT stack frees TX buffers from system workqueue,
  and to avoid blocking waiting to allocate, perform notify
  from a dedicated queue. | 
|  | * Avoid corruption by using work to process
  peripheral key position events on the main
  work thread, like local kscan events are.
* Fixes #221 | 
|  | closes #45 | 
|  | Removes the USB default under every split right half in favor of a default based on hardware capabilities in the main app Kconfig. | 
|  |  | 
|  |  | 
|  | * Move central/peripheral setting to Kconfig.defconfig
  files to allow left/right .conf files to override
  central/peripheral role for splits. | 
|  | * Refactor power to extract more general purpose
  activity detection/events.
* Use activity state to implement PM callback. | 
|  | See: https://docs.zephyrproject.org/latest/releases/release-notes-2.4.html
PR: #467 | 
|  |  | 
|  | * Battery and output status widgets
* Built in status screen combining them.
* Ability to define a custom status screen factory
  function. | 
|  | fix(ug): Don't return if finding ext power fails
fix(ug): Move ext_power to a static variable
Add #if defs | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | This PR adds support to control the external power output from controllers like nice!nano, nRFMicro etc
I have implemented based on my understanding of Pete suggestion on this feature.
Testing done:
    Tested by enabling and disabling the ext_power from application and verified
    Verified the application does not crash with boards that does not have ext_power support
    Note:
    I did not test this in nice!nano since I don't have the boards. Will get help from others once the behavior PR is up
Next Steps:
    Create a behavior PR to control enable/disable ext_power | 
|  | * New ZMK_SLEEP Kconfig symbol to enable the functionality.
* Switch to PORT events that allows wake from deep sleep.
* Initial basic power management policy, with idle ms,
  and ignoring deep sleep if we detect a USB connection. | 
|  |  | 
|  | * Proper max values for both split central, and
  non-split keyboards. | 
|  |  | 
|  | * Add back in profiles, not using Zephyr
  BT identity infrastructure.
* Restore additional `&bt` commands for profile
  operations.
* Fix for split pairing and subscriptions, since
  Zephyr persists subscriptions across connects.
* Remove keymap from peripheral builds, reduces
  firmware size, and avoids unneeded attempts
  to send HID data. | 
|  |  | 
|  | * Simplify the `bt` behavior to one current command
  `BT_CLEAR_BONDS_CMD`.
* Simplify BLE code for split and non-split keyboards.
* Remove keymap processing from split peripheral side. | 
|  |  | 
|  | * Add `bt` behavior that can be used to perform certain actions,
  such as next/prev identity, reset identity, etc.
  NOTE: Multiple identities is only supported for non-split shields,
  due to missing Zephyr identity functionality for dual
  central/peripheral devices.
* Proper bond reset tied to action, that honors peripheral bonds,
  so folks can reset and pair to other hosts, without breaking
  bonds between splt halves. | 
|  |  | 
|  |  | 
|  |  | 
|  | * Especially for splits, we need the ability to
  unpair all paired devices as  sledgehammer
  if we need to "reset things", and doing so via
  keymaps isn't suitable.
* Allows shields to define a collection of key
  positions that if all held 2 seconds after
  startup, will unpair all existing pairs for the
  device. | 
|  |  | 
|  |  | 
|  |  | 
|  | * Not working: Roll over + mod-tap with multiple
  mod-tap bindings! | 
|  | Initial RGB Underglow implementation | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | * Propogate key position state changes on central.
* Various BLE tweaks. | 
|  |  | 
|  |  | 
|  | * Service for split peripheral to report
  position state to split central.
* Updated advertising info.
* Behavior for split BT until we have a proper
  event system. | 
|  |  |