Searched refs:implemented (Results 1 – 25 of 587) sorted by relevance
12345678910>>...24
| /kernel/linux/linux-5.10/Documentation/arm/nwfpe/ |
| D | netwinder-fpe.rst | 28 These instructions are fully implemented.
40 These instructions are fully implemented. They store/load three words
58 FLT/FIX are fully implemented.
60 RFS/WFS are fully implemented.
62 RFC/WFC are fully implemented. RFC/WFC are supervisor only instructions, and
73 These are fully implemented.
87 These are fully implemented.
93 These are fully implemented as well. They use the same algorithm as the
103 This is fully implemented.
110 These are fully implemented.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | mlx5.rst | 7 This document describes the devlink features implemented by the ``mlx5``
13 .. list-table:: Generic parameters implemented
23 .. list-table:: Driver-specific parameters implemented
54 .. list-table:: devlink info versions implemented
|
| D | bnxt.rst | 7 This document describes the devlink features implemented by the ``bnxt``
13 .. list-table:: Generic parameters implemented
29 .. list-table:: Driver-specific parameters implemented
48 .. list-table:: devlink info versions implemented
|
| D | mlxsw.rst | 7 This document describes the devlink features implemented by the ``mlxsw``
13 .. list-table:: Generic parameters implemented
23 .. list-table:: Driver-specific parameters implemented
45 .. list-table:: devlink info versions implemented
|
| D | nfp.rst | 7 This document describes the devlink features implemented by the ``nfp``
13 .. list-table:: Generic parameters implemented
27 .. list-table:: devlink info versions implemented
|
| D | mlx4.rst | 7 This document describes the devlink features implemented by the ``mlx4``
13 .. list-table:: Generic parameters implemented
27 .. list-table:: Driver-specific parameters implemented
|
| D | qed.rst | 7 This document describes the devlink features implemented by the ``qed`` core
15 .. list-table:: Driver-specific parameters implemented
|
| D | ionic.rst | 7 This document describes the devlink features implemented by the ``ionic``
15 .. list-table:: devlink info versions implemented
|
| D | ti-cpsw-switch.rst | 7 This document describes the devlink features implemented by the ``ti-cpsw-switch``
16 .. list-table:: Driver-specific parameters implemented
|
| D | netdevsim.rst | 13 .. list-table:: Generic parameters implemented
23 .. list-table:: Driver-specific parameters implemented
34 can be implemented.
|
| D | mv88e6xxx.rst | 7 This document describes the devlink features implemented by the ``mv88e6xxx``
15 .. list-table:: Driver-specific parameters implemented
|
| D | sja1105.rst | 7 This document describes the devlink features implemented
13 .. list-table:: Driver-specific parameters implemented
|
| /kernel/linux/linux-5.10/drivers/phy/socionext/ |
| D | Kconfig | 13 Enable this to support USB PHY implemented on USB2 controller
25 Enable this to support USB PHY implemented in USB3 controller
35 Enable this to support PHY implemented in PCIe controller
45 Enable this to support PHY implemented in AHCI controller
|
| /kernel/linux/linux-5.10/arch/arm/crypto/ |
| D | Kconfig | 8 implemented using ARM specific CPU features or instructions.
17 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
27 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
37 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
46 SHA-256 secure hash standard (DFIPS 180-2) implemented
54 SHA-256 secure hash standard (DFIPS 180-2) implemented
62 SHA-512 secure hash standard (DFIPS 180-2) implemented
|
| /kernel/linux/linux-5.10/Documentation/networking/caif/ |
| D | linux_caif.rst | 33 * CAIF Link Layer, implemented as NET devices.
68 each layer described in the specification is implemented as a separate layer.
79 specification is implemented in a separate c-file.
179 The IP interface and CAIF socket API are implemented on top of the
189 The Link Layer is implemented as Linux network devices (struct net_device).
194 Therefore a flow-control mechanism is implemented where the physical
|
| /kernel/linux/linux-5.10/Documentation/i2c/busses/ |
| D | i2c-amd8111.rst | 35 Supported. Both PEC and block process call support is implemented. Slave
36 mode or host notification are not yet implemented.
|
| /kernel/linux/linux-5.10/Documentation/security/tpm/ |
| D | tpm_ftpm_tee.rst | 11 This driver is a shim for firmware implemented in ARM's TrustZone
19 implemented in firmware. The driver itself doesn't contain much logic and is
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | adt7475.rst | 82 * system acoustics optimizations (not implemented)
93 * 1 Imon input (not implemented)
94 * PECI support (not implemented)
95 * 2 GPIO pins (not implemented)
96 * system acoustics optimizations (not implemented)
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 38 This is implemented using READ_ONCE()/WRITE_ONCE() and
47 CPU (A-cumulative property). This is implemented using smp_mb().
54 (A-cumulative property). This is implemented using
61 after the acquire operation executes. This is implemented using
68 Control dependency on stores are not implemented using any explicit
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra194-tcu.txt | 4 systems within the Tegra SoC. It is implemented through a mailbox-
21 the mailbox subsystem, and the specifiers implemented by the relevant
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,nvic.txt | 4 Cortex-M based processor cores. The NVIC implemented on different SoCs
24 - arm,num-irq-priority-bits: The number of priority bits implemented by the
|
| /kernel/linux/linux-5.10/fs/ceph/ |
| D | caps.c | 658 cap->implemented = 0; in ceph_add_cap()
679 cap->issued = cap->implemented = CEPH_CAP_PIN; in ceph_add_cap()
767 cap->implemented |= issued; in ceph_add_cap()
808 int __ceph_caps_issued(struct ceph_inode_info *ci, int *implemented) in __ceph_caps_issued() argument
814 if (implemented) in __ceph_caps_issued()
815 *implemented = 0; in __ceph_caps_issued()
823 if (implemented) in __ceph_caps_issued()
824 *implemented |= cap->implemented; in __ceph_caps_issued()
833 have &= ~cap->implemented | cap->issued; in __ceph_caps_issued()
966 (cap->implemented & ~cap->issued & mask)) in __ceph_caps_revoking_other()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | ca_high_level.rst | 15 architecture can be implemented with this style, the definitions
51 implemented by most applications. Hence this area is revisited.
111 Not all ioctl's are implemented in the driver from the API, the other
112 features of the hardware that cannot be implemented by the API are achieved
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/ |
| D | dtv-core.rst | 6 Digital TV devices are implemented by several different drivers:
12 - Frontend drivers that are usually implemented as two separate drivers:
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | lan9303.rst | 13 The driver is implemented as a DSA driver, see ``Documentation/networking/dsa/dsa.rst``.
36 - Support for VLAN filtering is not implemented
|
12345678910>>...24