Searched refs:implemented (Results 1 – 25 of 722) sorted by relevance
12345678910>>...29
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.62 RFC/WFC are fully implemented. RFC/WFC are supervisor only instructions, and73 These are fully implemented.87 These are fully implemented.93 These are fully implemented as well. They use the same algorithm as the103 This is fully implemented.110 These are fully implemented.[all …]
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 implemented33 .. list-table:: Driver-specific parameters implemented52 .. list-table:: devlink info versions 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 ``zl3073x``13 .. list-table:: Generic parameters implemented29 .. 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 ``octeontx2 AF, PF and VF``15 .. list-table:: Driver-specific parameters implemented31 .. list-table:: Driver-specific parameters implemented67 .. list-table:: Driver-specific parameters 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 the15 .. list-table:: devlink info versions 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
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
37 * TODO: Remove this once RTC clock is implemented properly as part of67 /* TODO: Remove this once PMIC is implemented */143 /* TODO: Replace these once PMIC is implemented */161 /* TODO: Replace these once PMIC is 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
7 This document describes the devlink features implemented by the ``octeontx2 CPT``15 .. list-table:: Driver-specific parameters 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
35 Supported. Both PEC and block process call support is implemented. Slave36 mode or host notification are not yet implemented.
27 Each *ISP configuration block* is preceded by an header implemented by the56 Extension to the parameters format can be implemented by adding new blocks62 Support for generic statistics format is not yet implemented in Video4Linux2.
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