Changes in Makefile

007c3ff1 - crypto: caam - add in-kernel interface for blob generator

Fri, 13 May 2022 14:57:02 +0000

crypto: caam - add in-kernel interface for blob generatorThe NXP Cryptographic Acceleration and Assurance Module (CAAM)can be used to protect user-defined data across system reboot: - When the system is fused and boots into secure state, the master key is a unique never-disclosed device-specific key - random key is encrypted by key derived from master key - data is encrypted using the random key - encrypted data and its encrypted random key are stored alongside - This blob can now be safely stored in non-volatile memoryOn next power-on: - blob is loaded into CAAM - CAAM writes decrypted data either into memory or key registerAdd functions to realize encrypting and decrypting into memory alongsidethe CAAM driver.They will be used in a later commit as a source for the trusted keyseal/unseal mechanism.Reviewed-by: David Gstir Reviewed-by: Pankaj Gupta Tested-by: Tim Harvey Tested-by: Matthias Schiffer Tested-by: Pankaj Gupta Tested-by: Michael Walle # on ls1028a (non-E and E)Tested-by: John Ernberg # iMX8QXPSigned-off-by: Steffen Trumtrar Signed-off-by: Ahmad Fatoum Signed-off-by: Jarkko Sakkinen List of files: /linux-6.15/drivers/crypto/caam/Makefile

0aa6ac77 - crypto: caam/rng - Add support for PRNG

Fri, 29 Apr 2022 11:48:08 +0000

crypto: caam/rng - Add support for PRNGAdd support for random number generation using PRNGmode of CAAM and expose the interface through crypto API.According to the RM, the HW implementation of the DRBG followsNIST SP 800-90A specification for DRBG_Hash SHA-256 functionSigned-off-by: Meenakshi Aggarwal Reviewed-by: Horia Geant Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

abd98754 - crypto: caam - Move debugfs fops into standalone file

Thu, 06 Aug 2020 18:09:49 +0000

crypto: caam - Move debugfs fops into standalone fileCurrently the debugfs fops are defined in caam/intern.h. This causesproblems because it creates identical static functions and variablesin multiple files. It also creates warnings when those files don'tuse the fops.This patch moves them into a standalone file, debugfs.c.It also removes unnecessary uses of ifdefs on CONFIG_DEBUG_FS.Signed-off-by: Herbert Xu [Moved most of debugfs-related operations into debugfs.c.]Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

1c0ab408 - crypto: caam/qi2 - Add printing dpseci fq stats using debugfs

Tue, 23 Jul 2019 09:14:24 +0000

crypto: caam/qi2 - Add printing dpseci fq stats using debugfsAdd support of printing the dpseci frame queue statistics using debugfs.Signed-off-by: Vakul Garg Reviewed-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

1b46c90c - crypto: caam - convert top level drivers to libraries

Fri, 03 May 2019 14:17:39 +0000

crypto: caam - convert top level drivers to librariesCurrently we allow top level code, i.e. that which sits between thelow level (HW-specific) drivers and crypto API, to be built as severaldrivers: caamalg, caamhash, caam_pkc, caamrng, caamalg_qi.There is no advantage in this, more it interferes with adding supportfor deferred probing (there are no corresponding devices and thusno bus).Convert these drivers and call init() / exit() manually at the righttime.Move algorithms initialization at JR probe / remove time:-the first probed JR registers the crypto algs-the last removed JR unregisters the crypto algsNote: caam_qi_init() is called before JR platform devices creation(of_populate_bus()), such that QI interface is initialized whenthe caam/qi algorithms are registered in the JR driver (by callingcaam_qi_algapi_init().While here, fix the Kconfig entries under CRYPTO_DEV_FSL_CAAM_JRto be aligned.Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

0efa7579 - crypto: caam - export ahash shared descriptor generation

Wed, 12 Sep 2018 08:59:35 +0000

crypto: caam - export ahash shared descriptor generationcaam/qi2 driver will support ahash algorithms,thus move ahash descriptors generation in a shared location.Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

8d818c10 - crypto: caam/qi2 - add DPAA2-CAAM driver

Wed, 12 Sep 2018 08:59:33 +0000

crypto: caam/qi2 - add DPAA2-CAAM driverAdd CAAM driver that works using the DPSECI backend, i.e. managesDPSECI DPAA2 objects sitting on the Management Complex (MC) fsl-mc bus.Data transfers (crypto requests) are sent/received to/from CAAM cryptoengine via Queue Interface (v2), this being similar to existing caam/qi.OTOH, configuration/setup (obtaining virtual queue IDs, authorizationetc.) is done by sending commands to the MC f/w.Note that the CAAM accelerator included in DPAA2 platforms still hasJob Rings. However, the driver being added does not handle accessvia this backend. Kconfig & Makefile are updated such that DPAA2-CAAM(a.k.a. "caam/qi2") driver does not depend on caam/jr or caam/qibackends - which rely on platform bus support (ctrl.c).Support for the following aead and authenc algorithms is also addedin this patch:-aead:gcm(aes)rfc4106(gcm(aes))rfc4543(gcm(aes))-authenc:authenc(hmac({md5,sha*}),cbc({aes,des,des3_ede}))echainiv(authenc(hmac({md5,sha*}),cbc({aes,des,des3_ede})))authenc(hmac({md5,sha*}),rfc3686(ctr(aes))seqiv(authenc(hmac({md5,sha*}),rfc3686(ctr(aes)))Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/crypto/caam/Makefile

b189817c - crypto: caam/qi - add ablkcipher and authenc algorithms

Fri, 17 Mar 2017 10:06:02 +0000

crypto: caam/qi - add ablkcipher and authenc algorithmsAdd support to submit ablkcipher and authenc algorithmsvia the QI backend:-ablkcipher:cbc({aes,des,des3_ede})ctr(aes), rfc3686(ctr(aes))xts(aes)-authenc:authenc(hmac(md5),cbc({aes,des,des3_ede}))authenc(hmac(sha*),cbc({aes,des,des3_ede}))caam/qi being a new driver, let's wait some time to settle down withoutinterfering with existing caam/jr driver.Accordingly, for now all caam/qi algorithms (caamalg_qi module) aremarked to be of lower priority than caam/jr ones (caamalg module).Signed-off-by: Vakul Garg Signed-off-by: Alex Porosanu Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

67c2315d - crypto: caam - add Queue Interface (QI) backend support

Fri, 17 Mar 2017 10:06:01 +0000

crypto: caam - add Queue Interface (QI) backend supportCAAM engine supports two interfaces for crypto job submission:-job ring interface - already existing caam/jr driver-Queue Interface (QI) - caam/qi driver added in current patchQI is present in CAAM engines found on DPAA platforms.QI gets its I/O (frame descriptors) from QMan (Queue Manager) queues.This patch adds a platform device for accessing CAAM's queue interface.The requests are submitted to CAAM using one frame queue percryptographic context. Each crypto context has one shared descriptor.This shared descriptor is attached to frame queue associated withcorresponding driver context using context_a.The driver hides the mechanics of FQ creation, initialisation from itsapplications. Each cryptographic context needs to be associated withdriver context which houses the FQ to be used to transport the job toCAAM. The driver provides API for:(a) Context creation(b) Job submission(c) Context deletion(d) Congestion indication - whether path to/from CAAM is congestedThe driver supports affining its context to a particular CPU.This means that any responses from CAAM for the context in questionwould arrive at the given CPU. This helps in implementing one CPUper packet round trip in IPsec application.The driver processes CAAM responses under NAPI contexts.NAPI contexts are instantiated only on cores with affined portals sinceonly cores having their own portal can receive responses from DQRR.The responses from CAAM for all cryptographic contexts ride on a fixedset of FQs. We use one response FQ per portal owning core. The responseFQ is configured in each core's and thus portal's dedicated channel.This gives the flexibility to direct CAAM's responses for a cryptocontext on a given core.Signed-off-by: Vakul Garg Signed-off-by: Alex Porosanu Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

8cea7b66 - crypto: caam - refactor encryption descriptors generation

Tue, 22 Nov 2016 13:44:09 +0000

crypto: caam - refactor encryption descriptors generationRefactor the generation of the authenc, ablkcipher shared descriptorsand exports the functionality, such that they could be sharedwith the upcoming caam/qi (Queue Interface) driver.Signed-off-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

8c419778 - crypto: caam - add support for RSA algorithm

Mon, 04 Jul 2016 10:12:08 +0000

crypto: caam - add support for RSA algorithmAdd RSA support to caam driver.Initial author is Yashpal Dutta .Signed-off-by: Tudor Ambarus Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

6999d504 - crypto: caam - replace deprecated EXTRA_CFLAGS

Thu, 16 Jun 2016 13:32:55 +0000

crypto: caam - replace deprecated EXTRA_CFLAGSEXTRA_CFLAGS is still supported but its usage is deprecated.Signed-off-by: Tudor Ambarus Reviewed-by: Horia Geantă Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

313ea293 - crypto: caam - Add Platform driver for Job Ring

Fri, 25 Oct 2013 06:31:01 +0000

crypto: caam - Add Platform driver for Job RingThe SEC Job Rings are now available as individual devices.This would enable sharing of job rings between kernel anduser space. Job Rings can now be dynamically bound/unboundfrom kernel.Changes are made in the following layers of CAAM Driver1. Controller driver - Does basic initialization of CAAM Block. - Creates platform devices for Job Rings.(Earlier the initialization of Job ring was done by the controller driver)2. JobRing Platform driver - Manages the platform Job Ring devices created by the controller driverSigned-off-by: Ruchika Gupta Reviewed-by: Garg Vakul-B16394 Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

d4d8edf8 - crypto: caam - add option for enabling DEBUG mode

Wed, 14 Aug 2013 15:56:46 +0000

crypto: caam - add option for enabling DEBUG modeThis patch adds an option to the Kconfig file forSEC which enables the user to see the debug messagesthat are printed inside the SEC driver.Signed-off-by: Alex Porosanu Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

e24f7c9e - crypto: caam - hwrng support

Sat, 23 Jun 2012 00:48:50 +0000

crypto: caam - hwrng supportcaam_read copies random bytes from two buffers into output.caam rng can fill empty buffer 0xffff bytes at a time,but the buffer sizes are rounded down to multiple of cacheline size.Signed-off-by: Yuan Kang Signed-off-by: Kim Phillips Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

045e3678 - crypto: caam - ahash hmac support

Sat, 23 Jun 2012 00:48:47 +0000

crypto: caam - ahash hmac supportcaam supports ahash hmac with sha algorithms and md5.Signed-off-by: Yuan Kang Signed-off-by: Kim Phillips Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

4c1ec1f9 - crypto: caam - refactor key_gen, sg

Sat, 23 Jun 2012 00:48:45 +0000

crypto: caam - refactor key_gen, sgcreate separate files for split key generation and scatterlist functions.Signed-off-by: Yuan Kang Signed-off-by: Kim Phillips Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile

8e8ec596 - crypto: caam - Add support for the Freescale SEC4/CAAM

Sun, 13 Mar 2011 08:54:26 +0000

crypto: caam - Add support for the Freescale SEC4/CAAMThe SEC4 supercedes the SEC2.x/3.x as Freescale'sIntegrated Security Engine. Its programming model isincompatible with all prior versions of the SEC (talitos).The SEC4 is also known as the Cryptographic Acceleratorand Assurance Module (CAAM); this driver is named caam.This initial submission does not include support for Data Pathmode operation - AEAD descriptors are submitted via the jobring interface, while the Queue Interface (QI) is enabledfor use by others. Only AEAD algorithms are implementedat this time, for use with IPsec.Many thanks to the Freescale STC team for their contributionsto this driver.Signed-off-by: Steve Cornelius Signed-off-by: Kim Phillips Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/crypto/caam/Makefile