Searched refs:implemented (Results 1 – 25 of 744) sorted by relevance
12345678910>>...30
28 These instructions are fully implemented.40 These instructions are fully implemented. They store/load three words58 FLT/FIX are fully implemented.60 RFS/WFS are fully implemented.73 These are fully implemented.87 These are fully implemented.103 This is fully implemented.110 These are fully implemented.116 These are fully implemented.121 These are implemented. URD is implemented using the same code as the RND[all …]
7 This document describes the devlink features implemented by the ``octeontx2 AF, PF and VF``15 .. list-table:: Driver-specific parameters implemented31 .. list-table:: Driver-specific parameters implemented46 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``mlxsw``13 .. list-table:: Generic parameters implemented23 .. list-table:: Driver-specific parameters implemented45 .. list-table:: devlink info versions implemented66 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``bnxt``13 .. list-table:: Generic parameters implemented31 .. list-table:: Driver-specific parameters implemented50 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``mlx4``13 .. list-table:: Generic parameters implemented27 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``nfp``13 .. list-table:: Generic parameters implemented27 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``am65-cpsw-nuss``16 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``qed`` core15 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``ionic``15 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``ti-cpsw-switch``16 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``hns3``17 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``mv88e6xxx``15 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the15 .. list-table:: devlink info versions implemented
13 .. list-table:: Generic parameters implemented23 .. list-table:: Driver-specific parameters implemented34 can be implemented.
13 Enable this to support USB PHY implemented on USB2 controller25 Enable this to support USB PHY implemented in USB3 controller35 Enable this to support PHY implemented in PCIe controller45 Enable this to support PHY implemented in AHCI controller
80 Value of 0xff indicates that this option is not implemented91 Value of 0xff indicates that this option is not implemented102 Value of 0xffff indicates that this option is not implemented113 Value of 0xff indicates that this option is not implemented124 Value of 0xff indicates that this option is not implemented135 Value of 0xff indicates that this option is not implemented148 Value of 0xff indicates that this option is not implemented165 Value of 0xff indicates that this option is not implemented182 Value of 0xff indicates that this option is not implemented198 Value of 0xff indicates that this option is not implemented
7 This document describes the devlink features implemented by the ``octeontx2 CPT``15 .. list-table:: Driver-specific parameters implemented
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 the189 The Link Layer is implemented as Linux network devices (struct net_device).194 Therefore a flow-control mechanism is implemented where the physical
35 ports-implemented:59 - ports-implemented113 ports-implemented = <0x1>;
35 Supported. Both PEC and block process call support is implemented. Slave36 mode or host notification are not yet implemented.
38 This is implemented using READ_ONCE()/WRITE_ONCE() and47 CPU (A-cumulative property). This is implemented using smp_mb().54 (A-cumulative property). This is implemented using61 after the acquire operation executes. This is implemented using68 Control dependency on stores are not implemented using any explicit
57 /* TODO: Remove this once PMIC is implemented */63 /* TODO: Remove this once S2MPG11 slave PMIC is implemented */148 /* TODO: Update these once PMIC is implemented */
11 This driver is a shim for firmware implemented in ARM's TrustZone19 implemented in firmware. The driver itself doesn't contain much logic and is
37 implemented through a reserved region in BAR4.41 implemented as part of mailbox interface.
4 Cortex-M based processor cores. The NVIC implemented on different SoCs24 - arm,num-irq-priority-bits: The number of priority bits implemented by the
Completed in 32 milliseconds