feat(linux): Add crypto implementation options guide#746
Open
shiva-ti wants to merge 1 commit into
Open
Conversation
shiva-ti
requested review from
StaticRocket,
VeeruPrudhvi,
cshilwant,
gehariprasath,
jeevantelukula,
praneethbajjuri and
uditkumarti
as code owners
July 16, 2026 06:40
github-actions
Bot
assigned
bryanbrattlof,
devarsht,
gehariprasath,
jeevantelukula,
praneethbajjuri,
r-vignesh,
sskartheekadivi and
uditkumarti
|
New warnings found with rstcheck: |
shiva-ti
force-pushed
the
crypto_implementation
branch
from
July 16, 2026 06:44
80bbc64 to
8fdbb22
Compare
|
New warnings found with rstcheck: |
shiva-ti
force-pushed
the
crypto_implementation
branch
from
July 16, 2026 06:46
8fdbb22 to
f530a20
Compare
|
New warnings found with rstcheck: |
shiva-ti
force-pushed
the
crypto_implementation
branch
from
July 17, 2026 07:02
f530a20 to
289905a
Compare
|
New warnings found with rstcheck: |
Member
|
You uncovered a bit of a bug in that document. The sections at line 413 and 457 shouldn't have an overline. Could you correct that please? |
shiva-ti
force-pushed
the
crypto_implementation
branch
from
July 21, 2026 07:17
289905a to
9b163b3
Compare
StaticRocket
requested changes
Jul 21, 2026
shiva-ti
force-pushed
the
crypto_implementation
branch
from
July 22, 2026 06:26
9b163b3 to
2824add
Compare
StaticRocket
requested changes
Jul 23, 2026
StaticRocket
left a comment
StaticRocket
left a comment
Member
There was a problem hiding this comment.
Sorry, just caught these
Add documentation on crypto implementation options including hardware crypto accelerators and ARM-based crypto extensions, and the trade-offs of using them. Signed-off-by: Shiva Tripathi <s-tripathi1@ti.com>
shiva-ti
force-pushed
the
crypto_implementation
branch
from
July 24, 2026 15:19
2824add to
e3b007b
Compare
Collaborator
Author
thanks for pointing out, addressed those |
StaticRocket
approved these changes
Jul 24, 2026
ron-birkett
reviewed
Jul 27, 2026
| Crypto Implementation Options | ||
| ***************************** | ||
|
|
||
| Users can implement cryptographic operations by using one of the following approaches: |
Contributor
There was a problem hiding this comment.
Are the options mutually exclusive? i.e. can a user control how/when they use each? This writing makes it sound mutually exclusive.
ron-birkett
reviewed
Jul 27, 2026
|
|
||
| 2. **ARM CPU with Cryptographic Extension (ARM CE)** | ||
|
|
||
| - Uses ARM processor's built-in cryptographic hardware support |
Contributor
There was a problem hiding this comment.
Feel like this is unclear. DTHE is technically part of the ARM Processor in our case. Maybe if it was re-worded to ARM Core or ARM Instruction Set?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add documentation on crypto implementation options including hardware crypto accelerators and ARM-based crypto extensions, and the trade-offs of using them.