| /linux-4.4.14/drivers/atm/ |
| D | fore200e.c | 273 int scheme, magn, nbr; in fore200e_free_rx_buf() local
276 for (scheme = 0; scheme < BUFFER_SCHEME_NBR; scheme++) { in fore200e_free_rx_buf()
279 if ((buffer = fore200e->host_bsq[ scheme ][ magn ].buffer) != NULL) { in fore200e_free_rx_buf()
281 for (nbr = 0; nbr < fore200e_rx_buf_nbr[ scheme ][ magn ]; nbr++) { in fore200e_free_rx_buf()
297 int scheme, magn; in fore200e_uninit_bs_queue() local
299 for (scheme = 0; scheme < BUFFER_SCHEME_NBR; scheme++) { in fore200e_uninit_bs_queue()
302 struct chunk* status = &fore200e->host_bsq[ scheme ][ magn ].status; in fore200e_uninit_bs_queue()
303 struct chunk* rbd_block = &fore200e->host_bsq[ scheme ][ magn ].rbd_block; in fore200e_uninit_bs_queue()
951 int bsq_audit(int where, struct host_bsq* bsq, int scheme, int magn) in bsq_audit() argument
961 where, scheme, magn, buffer->index); in bsq_audit()
[all …]
|
| D | fore200e.h | 283 enum buffer_scheme scheme : 8, /* buffer scheme */
579 enum buffer_scheme scheme; /* buffer scheme */ member
883 enum buffer_scheme scheme; /* rx buffer scheme */ member
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | gpmc-nand.txt | 32 Refer below "How to select correct ECC scheme for your device ?"
95 How to select correct ECC scheme for your device ?
97 Higher ECC scheme usually means better protection against bit-flips and
98 increased system lifetime. However, selection of ECC scheme is dependent
110 Other factor which governs the selection of ecc-scheme is oob-size.
127 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
134 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
137 (OOBSIZE=128). So this device can use BCH16 ecc-scheme.
|
| D | gpmi-nand.txt | 27 ECC scheme.
|
| /linux-4.4.14/drivers/net/wireless/ath/ath9k/ |
| D | btcoex.c | 102 btcoex_hw->scheme = ATH_BTCOEX_CFG_NONE; in ath9k_hw_btcoex_init_scheme()
107 btcoex_hw->scheme = ATH_BTCOEX_CFG_MCI; in ath9k_hw_btcoex_init_scheme()
109 btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE; in ath9k_hw_btcoex_init_scheme()
118 btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE; in ath9k_hw_btcoex_init_scheme()
121 btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE; in ath9k_hw_btcoex_init_scheme()
370 if (btcoex_hw->scheme == ATH_BTCOEX_CFG_3WIRE) { in ath9k_hw_btcoex_disable()
|
| D | htc_drv_gpio.c | 176 if (ah->btcoex_hw.scheme == ATH_BTCOEX_CFG_3WIRE) in ath9k_htc_stop_btcoex()
192 ah->btcoex_hw.scheme = ATH_BTCOEX_CFG_NONE; in ath9k_htc_init_btcoex()
197 ah->btcoex_hw.scheme = ATH_BTCOEX_CFG_3WIRE; in ath9k_htc_init_btcoex()
|
| D | btcoex.h | 108 enum ath_btcoex_scheme scheme; member
|
| D | hw.h | 1163 return ah->btcoex_hw.scheme; in ath9k_hw_get_btcoex_scheme()
|
| /linux-4.4.14/net/decnet/ |
| D | TODO | 30 we have a half-way house scheme which seems to work reasonably well, but
31 the full scheme is still worth implementing, its not not top of my list
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | mandatory-locking.txt | 42 "advisory" locking scheme. However, the world isn't perfect, and there's
46 with a "mandatory" locking scheme, whereby the operating system kernel would
51 The System V mandatory locking scheme was intended to have as little impact as
52 possible on existing user code. The scheme is based on marking individual files
62 Note 2: POSIX.1 does not specify any scheme for mandatory locking, despite
63 borrowing the fcntl() locking scheme from System V. The mandatory locking
64 scheme is defined by the System V Interface Definition (SVID) Version 3.
|
| D | directory-locking | 1 Locking scheme used for directory operations is based on two
48 If no directory is its own ancestor, the scheme above is deadlock-free.
118 While this locking scheme works for arbitrary DAGs, it relies on
|
| D | f2fs.txt | 17 according to its internal geometry or flash memory management scheme, namely FTL,
385 F2FS adopts the checkpointing scheme to maintain file system consistency. At
545 tion. The copy-and-compaction scheme which is known as cleaning, is well-suited
548 overhead under high utilization. Contrarily, the threaded log scheme suffers
550 scheme where the copy-and-compaction scheme is adopted by default, but the
551 policy is dynamically changed to the threaded log scheme according to the file
|
| D | fiemap.txt | 41 flag is fatal to its operation. This scheme is intended to allow the
169 based addressing scheme. Since returning an extent for each block back to
|
| D | 00-INDEX | 45 - info about the locking scheme used for directory operations.
|
| D | qnx6.txt | 88 used. (scheme is the same as the one used for the superblock root nodes)
|
| D | squashfs.txt | 156 This scheme has the advantage that it doesn't require extra memory overhead
|
| D | vfat.txt | 264 legally fits within the old 8.3 encoding scheme does not have extra
|
| D | ext2.txt | 287 scheme but less reliable. Both methods are equally resolvable by their
|
| D | path-lookup.txt | 369 rcu-walk scheme, because some elements of the path may have been walked in
|
| D | Locking | 108 of the locking scheme for directory operations.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | qcom,spmi-pmic.txt | 4 PMICs. These PMICs use a QPNP scheme through SPMI interface.
5 QPNP is effectively a partitioning scheme for dividing the SPMI extended
|
| /linux-4.4.14/Documentation/scsi/ |
| D | aha152x.txt | 107 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
108 scheme instead. DOS expects a BIOS or driver that understands this
116 geometry just to be able to support that addressing scheme. The geometry
126 Moreover there are certain limitations to the C/H/S addressing scheme,
|
| D | in2000.txt | 48 memory management scheme in the 2.1.x kernel series.
|
| D | tmscsim.txt | 45 The numbering scheme isn't consistent. The first versions went from 1.00 to
46 1.12, then 1.20a to 1.20t. Finally I decided to use the ncr53c8xx scheme. So
|
| D | libsas.txt | 62 There is a scheme where the LLDD can RW certain fields,
|
| D | ChangeLog.ncr53c8xx | 256 scheme that allows up to 64 tags per LUN.
|
| D | BusLogic.txt | 330 the PCI BIOS enumeration, and requires that their scheme be supported by the
|
| D | ChangeLog.sym53c8xx | 248 - New linux-2.3.13 __setup scheme support added.
|
| D | ChangeLog.1992-1997 | 1202 scheme.
|
| /linux-4.4.14/Documentation/devicetree/bindings/power_supply/ |
| D | qnap-poweroff.txt | 9 Synology NAS devices use a similar scheme, but a different baud rate,
|
| /linux-4.4.14/fs/ceph/ |
| D | Kconfig | 35 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/fs/hfsplus/ |
| D | Kconfig | 21 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/fs/9p/ |
| D | Kconfig | 26 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/fs/ext2/ |
| D | Kconfig | 27 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | ti,tas5086.txt | 25 sequence, otherwise the default Low-Z scheme is used.
|
| /linux-4.4.14/Documentation/mtd/nand/ |
| D | pxa3xx-nand.txt | 55 So, repeating the above scheme, a 2048B data chunk will be followed by 32B
73 Because of the above scheme, and because the "spare" OOB is really located in
|
| /linux-4.4.14/drivers/staging/iio/light/ |
| D | isl29018.c | 243 static int isl29018_read_proximity_ir(struct isl29018_chip *chip, int scheme, in isl29018_read_proximity_ir() argument
253 scheme << COMMANDII_SCHEME_SHIFT); in isl29018_read_proximity_ir()
264 if (scheme == 1) { in isl29018_read_proximity_ir()
|
| /linux-4.4.14/fs/jfs/ |
| D | Kconfig | 17 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | locking.txt | 1 This file explains the locking and exclusion scheme used in the PCCARD
|
| /linux-4.4.14/Documentation/leds/ |
| D | leds-blinkm.txt | 17 The registration follows the scheme:
|
| D | leds-class.txt | 50 overhead, I suggest these become part of the device name. The naming scheme
|
| /linux-4.4.14/Documentation/mtd/ |
| D | spi-nor.txt | 15 receive bytes (Tx and Rx). Therefore, we must define a new layering scheme under
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | cpqarray.txt | 74 The device naming scheme is:
|
| D | cciss.txt | 70 The device naming scheme is:
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | cavium-pip.txt | 4 devices. The devices have a two level grouping scheme. There may be
|
| /linux-4.4.14/Documentation/dvb/ |
| D | udev.txt | 19 sysfs device name into the well known dvb adapter / device naming scheme.
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 24 "index-starts-at-one" modified the scheme as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm2835-armctrl-ic.txt | 4 72 interrupt sources using a 2-level register scheme. The interrupt
|
| /linux-4.4.14/drivers/i2c/busses/ |
| D | i2c-omap.c | 200 u16 scheme; member
1356 omap->scheme = OMAP_I2C_SCHEME(rev); in omap_i2c_probe()
1357 switch (omap->scheme) { in omap_i2c_probe()
1483 if (omap->scheme == OMAP_I2C_SCHEME_0) in omap_i2c_runtime_suspend()
|
| /linux-4.4.14/drivers/i2c/muxes/ |
| D | Kconfig | 14 I2C multimaster arbitration scheme using GPIOs and a challenge &
|
| /linux-4.4.14/tools/testing/selftests/futex/ |
| D | README | 53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
|
| /linux-4.4.14/Documentation/networking/ |
| D | driver.txt | 70 mitigation scheme to let TX packets "hang out" in the TX
|
| D | pktgen.txt | 75 with multi queue NICs, a the device naming scheme is extended with "@":
|
| D | README.sb1000 | 97 firewalling scheme.
|
| D | spider_net.txt | 184 The TX ring uses a low-watermark interrupt scheme to make sure that
|
| D | README.ipw2200 | 405 Releases are numbered with a three level scheme:
|
| D | l2tp.txt | 172 The driver supports a flexible debug scheme where kernel trace
|
| D | ppp_generic.txt | 183 scheme has the effect that more fragments are given to higher-
|
| D | arcnet-hardware.txt | 204 A basically different cabling scheme is used with Twisted Pair cabling. Each
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | sh_mobile_ceu_camera.txt | 12 Generic scaling / cropping scheme
|
| /linux-4.4.14/fs/f2fs/ |
| D | Kconfig | 48 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.txt | 11 Note that this scheme works well enough but has some downsides:
|
| /linux-4.4.14/fs/btrfs/ |
| D | Kconfig | 37 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/fs/reiserfs/ |
| D | Kconfig | 71 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/Documentation/ |
| D | ldm.txt | 11 Windows 2000, XP, and Vista use a new partitioning scheme. It is a complete
|
| D | atomic_ops.txt | 380 Given the above scheme, it must be the case that the obj->active
414 to a "hash table of spinlocks" scheme, that allows the full 32-bit
418 same scheme.
526 locking scheme is being used to protect the bitmask, and thus less
|
| D | unaligned-memory-access.txt | 98 parameters to a naturally aligned scheme, based on the size of the type of
117 For a natural alignment scheme, the compiler would only have to add a single
|
| D | pi-futex.txt | 116 Also, under this scheme, 'robustness' and 'PI' are two orthogonal
|
| D | vgaarbiter.txt | 18 control bus resources. Therefore an arbitration scheme outside of the X server
|
| D | IRQ-domain.txt | 33 reverse mapping scheme.
|
| D | dma-buf-sharing.txt | 400 scenarios, we can extend dma-buf with a more explicit cache tracking scheme
|
| D | kernel-parameters.txt | 967 auto selects the default scheme, which automatically
2291 scheme and the NFS level operations agree to use
3882 scheme (default 0 = off).
3889 [USB] Try the other device initialization scheme
|
| D | DMA-API-HOWTO.txt | 760 dynamic DMA mapping scheme - you have to always store the DMA addresses
|
| D | devices.txt | 3348 the System V/Unix98 naming scheme for PTYs, which assigns a common
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | graph.txt | 36 hardware interface, a common scheme using '#address-cells', '#size-cells'
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | README | 77 about your hardware and the TV sound scheme used in your country (or
|
| /linux-4.4.14/drivers/tty/serial/8250/ |
| D | 8250_omap.c | 506 u32 mvr, scheme; in omap_serial_fill_features_erratas() local
512 scheme = mvr >> OMAP_UART_MVR_SCHEME_SHIFT; in omap_serial_fill_features_erratas()
514 switch (scheme) { in omap_serial_fill_features_erratas()
|
| /linux-4.4.14/fs/xfs/ |
| D | Kconfig | 48 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/fs/ext4/ |
| D | Kconfig | 82 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | rockchip,pinctrl.txt | 51 cells should use the standard two-cell scheme described in
|
| /linux-4.4.14/block/partitions/ |
| D | Kconfig | 128 FreeBSD uses its own hard disk partition scheme on your PC. It
188 the limitations of the PC's partitioning scheme. The Logical Disk
|
| /linux-4.4.14/fs/ncpfs/ |
| D | Kconfig | 38 special applications which are able to utilize this locking scheme.
|
| /linux-4.4.14/Documentation/security/ |
| D | Smack.txt | 10 Smack is not the only Mandatory Access Control scheme
311 This scheme organizes users, programs, and data into domains that are
312 protected from each other. This scheme has been widely deployed as a component
314 maintain this scheme and the detailed understanding of the whole system
315 necessary to provide a secure domain mapping leads to the scheme being
322 LaPadula are addressed by providing a scheme whereby access can be controlled
|
| /linux-4.4.14/Documentation/trace/ |
| D | tracepoints.txt | 109 The naming scheme "subsys_event" is suggested here as a convention
|
| D | events.txt | 335 This scheme allows triggers to be invoked even for events that aren't
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | SoundPro | 104 - come up with a scheme which allows recording volumes for each subdevice.
|
| /linux-4.4.14/fs/jffs2/ |
| D | Kconfig | 83 groups beyond the owner/group/world scheme.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | cci.txt | 55 scheme to declare their register bases.
|
| D | cpus.txt | 49 scheme for processors that do not have a HW CPU
|
| /linux-4.4.14/drivers/tty/serial/ |
| D | omap-serial.c | 1482 u32 mvr, scheme; in omap_serial_fill_features_erratas() local
1488 scheme = mvr >> OMAP_UART_MVR_SCHEME_SHIFT; in omap_serial_fill_features_erratas()
1490 switch (scheme) { in omap_serial_fill_features_erratas()
|
| /linux-4.4.14/Documentation/vm/ |
| D | balance | 93 for a zone can be tracked and fed into the balancing scheme (jalvo@mbay.net)
|
| /linux-4.4.14/Documentation/aoe/ |
| D | aoe.txt | 142 to be pre-created using a static minor-number scheme with the
|
| /linux-4.4.14/Documentation/block/ |
| D | biovecs.txt | 16 In the new scheme of things, everything that must be mutated in order to
|
| D | data-integrity.txt | 98 concept of an end-to-end protection scheme is a layering violation.
|
| D | biodoc.txt | 183 a virtual address mapping (unlike the earlier scheme of virtual address
265 Arjan's proposed request priority scheme allows higher levels some broad
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | snapshot.txt | 82 A fixed naming scheme is used, so with the following commands:
|
| D | cache-policies.txt | 117 scheme we can decide how many entries occupy each multiqueue level,
|
| /linux-4.4.14/fs/ |
| D | Kconfig | 135 for users and groups beyond the standard owner/group/world scheme,
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig.txt | 193 blackbg => selects a color scheme with black background
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | decbin.S | 52 | greater than 10^27, a directed rounding scheme is used with
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 37 a common scheme using '#address-cells', '#size-cells' and 'reg' properties is
|
| /linux-4.4.14/drivers/tty/ |
| D | Kconfig | 112 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
147 terminals. This scheme has a number of problems, including
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Overview.txt | 168 the new rtc naming scheme.
|
| /linux-4.4.14/net/ipv6/netfilter/ |
| D | Kconfig | 23 Layer 3 independent connection tracking is experimental scheme
|
| /linux-4.4.14/Documentation/ia64/ |
| D | aliasing.txt | 53 scheme.
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 153 The reasoning behind this scheme is the observation that in the majority
172 PowerPC uses a slightly different scheme where it calls the .probe()
|
| D | booting-without-of.txt | 129 legacy iSeries platform breaks those rules as it predates this scheme,
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | cdrom-standard.tex | 77 scheme, either a separate driver had to be written, or an existing
319 the case in the old scheme). The register $mc_flags$ is used to buffer
504 old driver scheme. For example, you may look up the function
642 scheme, some \cdrom\ drivers don't do any integrity checking, resulting
740 driver scheme and option flag interpretation.
|
| /linux-4.4.14/drivers/scsi/fcoe/ |
| D | fcoe_ctlr.c | 1938 unsigned int scheme, unsigned int port) in fcoe_wwn_from_mac() argument
1952 wwn = host_mac | ((u64) scheme << 60); in fcoe_wwn_from_mac()
1953 switch (scheme) { in fcoe_wwn_from_mac()
|
| /linux-4.4.14/Documentation/thermal/ |
| D | intel_powerclamp.txt | 86 scheme to work for both preemptable and non-preemptable kernels.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | whatisRCU.txt | 424 o Use some solid scheme (such as locks or semaphores) to
993 the positive overhead of the interrupt-disabling scheme
994 with the zero-overhead RCU scheme does not constitute
|
| /linux-4.4.14/Documentation/fb/ |
| D | framebuffer.txt | 137 line, the X server will use the scheme discussed above, i.e. it will start
|
| /linux-4.4.14/net/netfilter/ipvs/ |
| D | Kconfig | 49 The IPVS connection hash table uses the chaining scheme to handle
|
| /linux-4.4.14/net/ipv4/netfilter/ |
| D | Kconfig | 23 Layer 3 independent connection tracking is experimental scheme
|
| /linux-4.4.14/fs/befs/ |
| D | ChangeLog | 216 * Thats right. New versioning scheme.
|
| /linux-4.4.14/Documentation/input/ |
| D | multi-touch-protocol.txt | 368 simple scheme, which is compatible with earlier usage, is:
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 98 scheme where individual function BARs can be "grouped" to fit in one or
|
| /linux-4.4.14/drivers/mtd/nand/ |
| D | Kconfig | 103 locate and correct errors when using BCH ECC scheme. This offloads
|
| /linux-4.4.14/Documentation/usb/ |
| D | gadget-testing.txt | 269 named following the <name>.<number> scheme. The numbers can be 0..8.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | sysfs-interface | 47 The common scheme for files naming is: <type><number>_<item>. Usual
|
| /linux-4.4.14/net/sched/ |
| D | Kconfig | 402 32bit pieces based comparison scheme.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 153 (now called mac80211) could be merged, a locking scheme needed to be
|
| D | 2.Process | 102 numbering scheme. To be considered for an update release, a patch must (1)
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README | 584 Same scheme is used with AT&E... at the tty's.
|
| /linux-4.4.14/Documentation/arm64/ |
| D | arm-acpi.txt | 116 of booting with either scheme (in kernels with both schemes enabled at compile
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1027 they are assigned hardware addresses using a different scheme which
1028 may conflict with the UML IP address-based scheme
1862 not. Using this scheme, the majority of data which is unchanged is
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 202 Layer 3 independent connection tracking is experimental scheme
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 365 * our batching and round-robin selection scheme
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 248 Our addressing scheme is basically as follows:
|
| /linux-4.4.14/ |
| D | CREDITS | 1365 D: original architect of the parallel-port sharing scheme
|