Swatantra-66 opened a new pull request, #21129:
URL: https://github.com/apache/nuttx/pull/21129

   *Note: This patch series is shepherded on behalf of off-GitHub contributor 
Kerogit (`[email protected]`) . Follow-up to merged PR #20677 and PR #20706.*
   
   ## Summary
   
   This patch adds emulated software interrupt functionality to the AVR DA/DB 
architecture. The chip itself does not have native software interrupts, so the 
suggested implementation manipulates an I/O pin configured to trigger a 
hardware interrupt. The implementation can serve multiple users simultaneously 
and supports sharing the hardware interrupt of the I/O port with other users.
   
   There is no in-tree user of this functionality yet; the intended user is a 
follow-up patch series providing a driver for the WS2812 programmable LED.
   
   ## Impact
   
   * **New feature**: Software interrupt emulation for the AVR DA/DB family.
   * **Impact on user**: None, new code is not enabled by default. Other AVR 
families are not supported and not affected.
   * **Impact on build**: New Kconfig options related to the feature, none 
otherwise.
   * **Impact on documentation**: Zero latency interrupts guide updated 
(mentions software interrupt emulation as a way to "get back into the game").
   * **Impact on hardware / security / compatibility**: None.
   
   ## Testing
   
   Verified on local setup by author (`Kerogit <[email protected]>`):
   * **Build Host(s)**: Linux, AMD, GCC avr-gcc 14.2
   * **Target(s)**: AVR DA/DB, tested on `breadxavr`
   * Tested with the WS2812 driver which uses this functionality to notify the 
OS that data transmission performed by the zero latency interrupt handler is 
complete.
   * Documentation verified with `make html`; all source code changes verified 
with `checkpatch.sh`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to