Searched refs:schemes (Results 1 – 25 of 33) sorted by relevance
12
| /Linux-v5.10/Documentation/devicetree/bindings/mtd/ |
| D | gpmc-nand.txt | 113 support ecc-schemes with hardware error-correction (BCHx_HW). However
114 such SoC can use ecc-schemes with software library for error-correction
121 Higher ECC schemes require more OOB/Spare area to store ECC syndrome,
131 '3' for HAM1_xx ecc schemes
132 '7' for BCH4_xx ecc schemes
133 '14' for BCH8_xx ecc schemes
134 '26' for BCH16_xx ecc schemes
141 probably use lower ecc-schemes like BCH8.
|
| /Linux-v5.10/drivers/net/ethernet/freescale/fman/ |
| D | fman_keygen.c | 257 struct keygen_scheme schemes[FM_KG_MAX_NUM_OF_SCHEMES]; member
450 if (!keygen->schemes[i].used) { in get_free_scheme_id()
472 return &keygen->schemes[scheme_id]; in get_scheme()
|
| /Linux-v5.10/Documentation/mips/ |
| D | booting.rst | 8 Both schemes are supported; CONFIG_BOOT_RAW=y and CONFIG_NO_EXCEPT_FILL=y,
|
| /Linux-v5.10/security/smack/ |
| D | Kconfig | 13 of other mandatory security schemes.
|
| /Linux-v5.10/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 348 Computer systems employ a variety of schemes to constrain how information is
349 shared among the people and services using the machine. Some of these schemes
351 access to pieces of data. These schemes are called discretionary access
353 of the user. Other schemes do not leave the decision regarding what a user or
354 program can access up to users or programs. These schemes are called mandatory
502 be "born" highly classified. To accommodate such schemes Smack includes a
552 schemes and concepts from other systems. Most often, the other systems are
650 of systems that use compatible labeling schemes, and the DOI specified on the
|
| /Linux-v5.10/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 17 are dictated by the binding of the reset provider, although common schemes
|
| /Linux-v5.10/Documentation/driver-api/fpga/ |
| D | fpga-region.rst | 19 is intended to be used by other schemes that have other ways of accomplishing
|
| /Linux-v5.10/Documentation/infiniband/ |
| D | tag_matching.rst | 25 Implementations frequently use different matching schemes for these two
|
| /Linux-v5.10/fs/f2fs/ |
| D | Kconfig | 17 the internal geometry or flash memory management schemes aka FTL, F2FS
|
| /Linux-v5.10/Documentation/i2c/ |
| D | fault-codes.rst | 13 faults. There may be fancier recovery schemes that are appropriate in
|
| /Linux-v5.10/Documentation/driver-api/gpio/ |
| D | intro.rst | 50 value might be driven, supporting "wire-OR" and similar schemes for the
|
| /Linux-v5.10/Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 93 schemes and finally this heavily impacts external debug module. So we can
|
| /Linux-v5.10/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-isku | 149 Description: When written, this file lets one trigger temporary color schemes
|
| /Linux-v5.10/Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 80 schemes. This bit is stored in bit 6 of the scancode, inverted. This is
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | dma-buf.rst | 203 Common to all these schemes is that userspace controls the dependencies of these
|
| D | mtdnand.rst | 611 has built in default placement schemes for the various chiptypes. If due
618 Placement schemes are defined by a nand_oobinfo structure
690 Spare area autoplacement default schemes
|
| /Linux-v5.10/block/partitions/ |
| D | Kconfig | 14 the questions about foreign partitioning schemes.
|
| /Linux-v5.10/Documentation/block/ |
| D | data-integrity.rst | 22 for some protection schemes also that the I/O is written to the right
|
| /Linux-v5.10/Documentation/core-api/ |
| D | pin_user_pages.rst | 156 the pages. There may be other possible schemes, such as for example explicitly
|
| /Linux-v5.10/net/ipv4/ |
| D | Kconfig | 479 bounded TCP-friendliness. The protocol combines two schemes
669 AQM schemes that do not provide a delay signal. It requires the fq
|
| /Linux-v5.10/Documentation/networking/ |
| D | j1939.rst | 106 address being claimed. This serves as a base for filter schemes. By default,
|
| D | arcnet.rst | 467 schemes that rely completely on the netmask and a 'default gateway' to
|
| /Linux-v5.10/drivers/md/ |
| D | Kconfig | 257 Some bio locking schemes used by other device-mapper targets
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | relay.rst | 270 easily implement random-access-on-buffer-boundary schemes, which can
|
| /Linux-v5.10/Documentation/arm64/ |
| D | arm-acpi.rst | 118 of booting with either scheme (in kernels with both schemes enabled at compile
|
12
