| /Linux-v5.4/drivers/net/ethernet/freescale/fman/ |
| D | fman_keygen.c | 490 struct keygen_scheme *scheme; in keygen_bind_port_to_schemes() local
495 scheme = get_scheme(keygen, scheme_id); in keygen_bind_port_to_schemes()
496 if (!scheme) { in keygen_bind_port_to_schemes()
500 if (!scheme->used) { in keygen_bind_port_to_schemes()
507 ar_reg = build_ar_bind_scheme(scheme->hw_port_id, false); in keygen_bind_port_to_schemes()
516 ar_reg = build_ar_bind_scheme(scheme->hw_port_id, true); in keygen_bind_port_to_schemes()
541 struct keygen_scheme *scheme; in keygen_scheme_setup() local
545 scheme = get_scheme(keygen, scheme_id); in keygen_scheme_setup()
546 if (!scheme) { in keygen_scheme_setup()
550 if (enable && scheme->used) { in keygen_scheme_setup()
[all …]
|
| /Linux-v5.4/drivers/atm/ |
| D | fore200e.c | 291 int scheme, magn, nbr; in fore200e_free_rx_buf() local
294 for (scheme = 0; scheme < BUFFER_SCHEME_NBR; scheme++) { in fore200e_free_rx_buf()
297 if ((buffer = fore200e->host_bsq[ scheme ][ magn ].buffer) != NULL) { in fore200e_free_rx_buf()
299 for (nbr = 0; nbr < fore200e_rx_buf_nbr[ scheme ][ magn ]; nbr++) { in fore200e_free_rx_buf()
315 int scheme, magn; in fore200e_uninit_bs_queue() local
317 for (scheme = 0; scheme < BUFFER_SCHEME_NBR; scheme++) { in fore200e_uninit_bs_queue()
320 struct chunk* status = &fore200e->host_bsq[ scheme ][ magn ].status; in fore200e_uninit_bs_queue()
321 struct chunk* rbd_block = &fore200e->host_bsq[ scheme ][ magn ].rbd_block; in fore200e_uninit_bs_queue()
862 int bsq_audit(int where, struct host_bsq* bsq, int scheme, int magn) in bsq_audit() argument
872 where, scheme, magn, buffer->index); in bsq_audit()
[all …]
|
| D | fore200e.h | 284 enum buffer_scheme scheme : 8, /* buffer scheme */
580 enum buffer_scheme scheme; /* buffer scheme */ member
878 enum buffer_scheme scheme; /* rx buffer scheme */ member
|
| /Linux-v5.4/Documentation/devicetree/bindings/mtd/ |
| D | gpmc-nand.txt | 35 Refer below "How to select correct ECC scheme for your device ?"
105 How to select correct ECC scheme for your device ?
107 Higher ECC scheme usually means better protection against bit-flips and
108 increased system lifetime. However, selection of ECC scheme is dependent
120 Other factor which governs the selection of ecc-scheme is oob-size.
137 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
144 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
147 (OOBSIZE=128). So this device can use BCH16 ecc-scheme.
|
| /Linux-v5.4/drivers/net/wireless/ath/ath9k/ |
| D | btcoex.c | 120 if (btcoex_hw->scheme != ATH_BTCOEX_CFG_2WIRE && in ath9k_hw_btcoex_pin_init()
121 btcoex_hw->scheme != ATH_BTCOEX_CFG_3WIRE) in ath9k_hw_btcoex_pin_init()
146 btcoex_hw->scheme = ATH_BTCOEX_CFG_NONE; in ath9k_hw_btcoex_init_scheme()
151 btcoex_hw->scheme = ATH_BTCOEX_CFG_MCI; in ath9k_hw_btcoex_init_scheme()
153 btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE; in ath9k_hw_btcoex_init_scheme()
160 btcoex_hw->scheme = ATH_BTCOEX_CFG_3WIRE; in ath9k_hw_btcoex_init_scheme()
162 btcoex_hw->scheme = ATH_BTCOEX_CFG_2WIRE; in ath9k_hw_btcoex_init_scheme()
434 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 | gpio.c | 404 enum ath_btcoex_scheme scheme = ath9k_hw_get_btcoex_scheme(ah); in ath9k_deinit_btcoex() local
406 if (scheme == ATH_BTCOEX_CFG_2WIRE || in ath9k_deinit_btcoex()
407 scheme == ATH_BTCOEX_CFG_3WIRE) in ath9k_deinit_btcoex()
|
| /Linux-v5.4/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-v5.4/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.rst | 6 Locking scheme used for directory operations is based on two
65 If no directory is its own ancestor, the scheme above is deadlock-free.
136 While this locking scheme works for arbitrary DAGs, it relies on
|
| /Linux-v5.4/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-v5.4/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,
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | ifork.rst | 36 Note that with this block mapping scheme, it is necessary to fill out a
38 led to the creation of the extent mapping scheme, discussed below.
40 Notice also that a file using this mapping scheme cannot be placed
47 tree. Under the old scheme, allocating a contiguous run of 1,000 blocks
|
| D | allocators.rst | 25 Under this scheme, when a file needs more blocks to absorb file writes,
51 this scheme evens out the loading on the block groups, though the author
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/reset/ |
| D | qnap-poweroff.txt | 8 Synology NAS devices use a similar scheme, but a different baud rate,
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ti/ |
| D | k3.txt | 5 shall follow the following scheme:
|
| /Linux-v5.4/Documentation/iio/ |
| D | ep93xx_adc.rst | 15 Numbering scheme for channels 0..4 is defined in EP9301 and EP9302 datasheets.
|
| /Linux-v5.4/Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra186-bpmp.txt | 53 services. Put another way, the numbering scheme for I2C buses is distinct from
54 the numbering scheme for any other service the BPMP may provide (e.g. a future
|
| /Linux-v5.4/fs/9p/ |
| D | Kconfig | 27 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/fs/ext2/ |
| D | Kconfig | 27 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | ti,tas5086.txt | 25 sequence, otherwise the default Low-Z scheme is used.
|
| /Linux-v5.4/fs/ceph/ |
| D | Kconfig | 36 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/drivers/iio/light/ |
| D | isl29018.c | 224 static int isl29018_read_proximity_ir(struct isl29018_chip *chip, int scheme, in isl29018_read_proximity_ir() argument
235 scheme << ISL29018_CMD2_SCHEME_SHIFT); in isl29018_read_proximity_ir()
246 if (scheme == 1) { in isl29018_read_proximity_ir()
|
| /Linux-v5.4/fs/jfs/ |
| D | Kconfig | 18 groups beyond the owner/group/world scheme.
|
