eren-terzioglu opened a new pull request, #16692: URL: https://github.com/apache/nuttx/pull/16692
## Summary Add SHA Accelator peripheral support for Espressif devices to hash blocks fast and efficiently. <!-- This field should contain a summary of the changes. It will be pre-filled with the commit's message and descriptions. Adjust it accordingly --> * Docs/espressif: Add crypto defconfig docs for esp32[-s2|-s3] Docs/espressif: Add crypto defconfig docs for Xtensa based Espressif devices * boards/xtensa: Add board layer SHA accelerator support for esp32[-s2|-s3] Add board layer SHA accelerator support for Xtensa based Espressif devices * arch/xtensa: Add arch layer SHA accelerator support for esp32[-s2|-s3] Add arch layer SHA accelerator support for Xtensa based Espressif devices * Docs/espressif: Add crypto defconfig docs for esp32[-c3|-c6|-h2] Docs/espressif: Add crypto defconfig docs for risc-v based Espressif chips * boards/risc-v: Add board layer SHA accelerator support for esp32[-c3|-c6|-h2] Add board layer SHA accelerator support for risc-v based Espressif devices * arch/risc-v: Add arch layer SHA accelerator support for esp32[-c3|-c6|-h2] Add arch layer SHA accelerator support for risc-v based Espressif devices ## Impact <!-- Please fill the following sections with YES/NO and provide a brief explanation --> Impact on user: Yes, new peripheral support added <!-- Does it impact user's applications? How? --> Impact on build: No <!-- Does it impact on building NuttX? How? (please describe the required changes on the build system) --> Impact on hardware: Yes, SHA accelerator can be used for Espressif devices <!-- Does it impact a specific hardware supported by NuttX? --> Impact on documentation: Yes, crypto defconfig docs added <!-- Does it impact the existing documentation? Please provide additional documentation to reflect that --> Impact on security: No <!-- Does it impact NuttX's security? --> Impact on compatibility: No, it is compatible <!-- Does it impact compatibility between previous and current versions? Is this a breaking change? --> ## Testing <!-- Please provide all the testing procedure. Consider that upstream reviewers should be able to reproduce the same testing performed internally --> ### Building <!-- Provide how to build the test for each SoC being tested --> Command used to build: ``` make distclean; ./tools/configure.sh esp32c6-devkitc:crypto; make -j; make download ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BAUD=921600 ESPTOOL_BINDIR=../esp-bins/ ``` ``` make distclean; ./tools/configure.sh esp32s3-devkit:crypto; make -j; make download ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BAUD=921600 ESPTOOL_BINDIR=../esp-bins/ ``` ### Running <!-- Provide how to run the test for each SoC being tested --> `hmac` example used to test ### Results <!-- Provide tests' results and runtime logs --> Output should look like this: ``` ... nsh> hmac ... hmac sha1 success hmac sha1 success hmac sha1 success hmac sha256 success hmac sha256 success hmac sha256 success ``` -- 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: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
