| /OK3568_Linux_fs/kernel/lib/crypto/ |
| H A D | Kconfig | 15 accelerated implementation of the Blake2s library interface, 24 implementation is enabled, this implementation serves the users 31 accelerated implementation of the ChaCha library interface, 40 implementation is enabled, this implementation serves the users 50 by either the generic implementation or an arch-specific one, if one 57 accelerated implementation of the Curve25519 library interface, 66 implementation is enabled, this implementation serves the users 76 fulfilled by either the generic implementation or an arch-specific 93 accelerated implementation of the Poly1305 library interface, 102 implementation is enabled, this implementation serves the users [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/arm/samsung/ |
| H A D | gpio.rst | 2 Samsung GPIO implementation 8 This outlines the Samsung GPIO implementation and the architecture 16 about these devices. Their implementation has been brought into line 17 with the core samsung implementation described in this document. 23 The gpio implementation uses gpiolib as much as possible, only providing 35 implementation to configure pins as necessary.
|
| /OK3568_Linux_fs/kernel/Documentation/crypto/ |
| H A D | architecture.rst | 103 the following implementations: AES-NI, assembler implementation, or 105 which cipher implementation is used? The answer to that question is the 106 priority number assigned to each cipher implementation by the kernel 109 implementations providing an implementation with that name and selects 110 the implementation with the highest priority. 113 implementation and thus does not want to rely on the priority-based 115 the cipher implementation to register a unique name in addition to 117 sure to refer to the intended cipher implementation. 133 - module: the kernel module providing the cipher implementation (or 136 - priority: the priority value of the cipher implementation [all …]
|
| /OK3568_Linux_fs/kernel/drivers/mailbox/ |
| H A D | Kconfig | 23 Mailbox implementation for i.MX Messaging Unit (MU). 39 An implementation of the ARM PL320 Interprocessor Communication 50 Mailbox implementation for communication with the the firmware 59 Mailbox implementation for OMAP family chips with hardware for 98 An implementation of the Altera Mailbox soft core. It is used 106 An implementation of the BCM2385 Mailbox. It is used to invoke 114 Mailbox implementation for STMicroelectonics family chips with 121 An implementation of Message Manager slave driver for Keystone 134 An implementation of the hi3660 mailbox. It is used to send message 144 An implementation of the hi6220 mailbox. It is used to send message [all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/crypto/ |
| H A D | Kconfig | 71 slower than the NEON implementation of BLAKE2b. (There is no NEON 72 implementation of BLAKE2s, since NEON doesn't really help with it.) 81 Crypto Extensions, typically this BLAKE2b implementation is 92 fastest AES implementation for single blocks. For multiple 93 blocks, the NEON bit-sliced implementation is usually faster. 95 This implementation may be vulnerable to cache timing attacks, 109 Use a faster and more secure NEON based implementation of AES in CBC, 115 This implementation does not rely on any lookup tables so it is 125 Use an implementation of AES in CBC, CTR and XTS modes that uses 135 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
|
| /OK3568_Linux_fs/kernel/drivers/video/fbdev/nvidia/ |
| H A D | nv_setup.c | 233 u32 implementation = par->Chipset & 0x0ff0; in nv10GetConfig() local 264 if (par->twoHeads && (implementation != 0x0110)) { in nv10GetConfig() 278 u16 implementation = par->Chipset & 0x0ff0; in NVCommonSetup() local 315 (implementation != 0x0100) && in NVCommonSetup() 316 (implementation != 0x0150) && in NVCommonSetup() 317 (implementation != 0x01A0) && (implementation != 0x0200); in NVCommonSetup() 320 (implementation != 0x0110)); in NVCommonSetup() 322 par->twoStagePLL = (implementation == 0x0310) || in NVCommonSetup() 323 (implementation == 0x0340) || (par->Architecture >= NV_ARCH_40); in NVCommonSetup() 326 (implementation != 0x0100); in NVCommonSetup() [all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/ |
| H A D | charconv | 106 // Generic implementation for arbitrary bases. 117 // Generic implementation for arbitrary bases. 122 static_assert(is_integral<_Tp>::value, "implementation bug"); 123 static_assert(is_unsigned<_Tp>::value, "implementation bug"); 163 static_assert(is_integral<_Tp>::value, "implementation bug"); 164 static_assert(is_unsigned<_Tp>::value, "implementation bug"); 210 static_assert(is_integral<_Tp>::value, "implementation bug"); 211 static_assert(is_unsigned<_Tp>::value, "implementation bug"); 234 static_assert(is_integral<_Tp>::value, "implementation bug"); 235 static_assert(is_unsigned<_Tp>::value, "implementation bug"); [all …]
|
| H A D | execution | 36 // Algorithm implementation 41 // Numeric implementation 46 // Memory implementation
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/ |
| H A D | charconv | 106 // Generic implementation for arbitrary bases. 117 // Generic implementation for arbitrary bases. 122 static_assert(is_integral<_Tp>::value, "implementation bug"); 123 static_assert(is_unsigned<_Tp>::value, "implementation bug"); 163 static_assert(is_integral<_Tp>::value, "implementation bug"); 164 static_assert(is_unsigned<_Tp>::value, "implementation bug"); 210 static_assert(is_integral<_Tp>::value, "implementation bug"); 211 static_assert(is_unsigned<_Tp>::value, "implementation bug"); 234 static_assert(is_integral<_Tp>::value, "implementation bug"); 235 static_assert(is_unsigned<_Tp>::value, "implementation bug"); [all …]
|
| H A D | execution | 36 // Algorithm implementation 41 // Numeric implementation 46 // Memory implementation
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | genericirq.rst | 28 The original implementation of interrupt handling in Linux uses the 33 a quite universal set for the ARM interrupt handler implementation in 42 During the implementation we identified another type: 51 This split implementation of high-level IRQ handlers allows us to 56 The original general IRQ implementation used hw_interrupt_type 76 flow handler implementation also makes it simple to provide 82 IRQ-flow implementation for 'level type' interrupts and add a 83 (sub)architecture specific 'edge type' implementation. 225 handle_level_irq provides a generic implementation for level-triggered 238 handle_fasteoi_irq provides a generic implementation for interrupts, [all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pyjwt_2.3.0.bb | 1 SUMMARY = "JSON Web Token implementation in Python" 2 DESCRIPTION = "A Python implementation of JSON Web Token draft 32.\ 3 Original implementation was written by https://github.com/progrium"
|
| /OK3568_Linux_fs/external/xserver/miext/rootless/ |
| H A D | README.txt | 22 implementation, which provides functions that allow the generic rootless 40 frames, this must be done by the rootless implementation. The generic 43 the rootless implementation's StartDrawing() function and StopDrawing() 60 generic rootless layer through rootless implementation functions, compile- 61 time options, and runtime parameters. The rootless implementation 64 frames. Some of the implementation functions are optional. A detailed 65 description of the rootless implementation functions is provided in 68 By design, a rootless implementation should only have to include 71 rootlessCommon.h in your implementation, let the generic rootless layer 73 should be generalized.) A rootless implementation should also modify [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A D | x25.rst | 8 write an X.25 implementation for Linux. My aim is to provide a complete X.25 15 I therefore decided to write the implementation such that as far as the 18 implementation of LAPB. Therefore the LAPB modules would be called by 22 To confuse matters a little, an 802.2 LLC implementation for Linux is being 27 implementation is being done as part of another protocol project (SNA) and
|
| H A D | sctp.rst | 8 implementation. 21 The initial project goal is to create an Linux kernel reference implementation 33 implementation and testing lksctp on IPv4.
|
| /OK3568_Linux_fs/buildroot/package/swupdate/ |
| H A D | swupdate.config | 70 # Hash checking needs an SSL implementation 74 # Image signature verification needs an SSL implementation 78 # Image encryption needs an SSL implementation 86 # SSL support needs an SSL implementation
|
| /OK3568_Linux_fs/buildroot/package/python3/ |
| H A D | 0011-Add-importlib-fix-for-PEP-3147-issue.patch | 35 - If sys.implementation.cache_tag is None then NotImplementedError is raised. 44 - tag = sys.implementation.cache_tag 46 - raise NotImplementedError('sys.implementation.cache_tag is None') 66 - sys.implementation.cache_tag is None then NotImplementedError is raised. 70 - if sys.implementation.cache_tag is None: 71 - raise NotImplementedError('sys.implementation.cache_tag is None')
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/location/labs/qsg/ |
| H A D | qgeomapobjectqsgsupport.cpp | 73 …pPolylineObjectPrivate &oldImpl = static_cast<QMapPolylineObjectPrivate &>(*obj->implementation()); in createMapObjectImplementationPrivate() 81 …MapPolygonObjectPrivate &oldImpl = static_cast<QMapPolygonObjectPrivate &>(*obj->implementation()); in createMapObjectImplementationPrivate() 89 … QMapCircleObjectPrivate &oldImpl = static_cast<QMapCircleObjectPrivate &>(*obj->implementation()); in createMapObjectImplementationPrivate() 97 … QMapRouteObjectPrivate &oldImpl = static_cast<QMapRouteObjectPrivate &>(*obj->implementation()); in createMapObjectImplementationPrivate() 105 … QMapIconObjectPrivate &oldImpl = static_cast<QMapIconObjectPrivate &>(*obj->implementation()); in createMapObjectImplementationPrivate()
|
| /OK3568_Linux_fs/u-boot/drivers/usb/ulpi/ |
| H A D | Kconfig | 7 Select ULPI viewport (SoC-side interface to ULPI) implementation 14 Support generic ULPI Viewport implementation that is used on 20 Support ULPI Viewport implementation that is used on OMAP devices.
|
| /OK3568_Linux_fs/u-boot/drivers/pinctrl/nxp/ |
| H A D | Kconfig | 15 this is a simple implementation, only parses the 'fsl,pins' 29 this is a simple implementation, only parses the 'fsl,pins' 43 this is a simple implementation, only parses the 'fsl,pins' 56 is different from the linux one, this is a simple implementation,
|
| /OK3568_Linux_fs/external/rknpu2/examples/rknn_yolov5_android_apk_demo/app/ |
| H A D | build.gradle | 50 implementation fileTree(dir: 'libs', include: ['*.jar']) 51 implementation 'com.android.support:appcompat-v7:28.0.0' 52 implementation 'com.android.support.constraint:constraint-layout:2.0.4'
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.omap-ulpi-viewport | 12 implementation of "drivers/usb/ulpi/ulpi.c" 20 omap-ulpi-viewport implementation. 26 implementation which will do ulpi reset using the
|
| H A D | README.sdp | 9 The implementation in U-Boot uses the USB Downloader Gadget (g_dnl) to 10 provide a SDP implementation over USB. This allows to download program 16 U-Boot implementation has primarly been tested using the open source 28 This implementation can be started in U-Boot using the sdp command 34 detection the SPL will run the SDP implementation automatically in
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A D | men-chameleon-bus.rst | 9 1.2 Limitations of the current implementation 26 This document describes the architecture and implementation of the MEN 33 implementation and does by no means describe the complete possibilities of MCB 36 Limitations of the current implementation 39 The current implementation is limited to PCI and PCIe based carrier devices 68 not handled by the MCB implementation. 97 The current implementation assigns exactly one memory and one IRQ resource
|
| /OK3568_Linux_fs/u-boot/drivers/power/regulator/ |
| H A D | Kconfig | 50 This config enables implementation of driver-model regulator uclass 76 This config enables implementation of driver-model regulator uclass 84 This config enables implementation of driver-model regulator uclass 92 This config enables implementation of driver-model regulator uclass 99 This config enables implementation of driver-model regulator uclass 182 This enables implementation of driver-model regulator uclass 190 This enables implementation of driver-model regulator uclass 198 This enables implementation of driver-model regulator uclass
|