Home
last modified time | relevance | path

Searched full:parameters (Results 1 – 25 of 2799) sorted by relevance

12345678910>>...112

/linux/Documentation/driver-api/dmaengine/
H A Ddmatest.rst48 % echo 2000 > /sys/module/dmatest/parameters/timeout
49 % echo 1 > /sys/module/dmatest/parameters/iterations
50 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
51 % echo 1 > /sys/module/dmatest/parameters/run
60 % echo 2000 > /sys/module/dmatest/parameters/timeout
61 % echo 1 > /sys/module/dmatest/parameters/iterations
62 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
63 % echo dma0chan1 > /sys/module/dmatest/parameters/channel
64 % echo dma0chan2 > /sys/module/dmatest/parameters/channel
65 % echo 1 > /sys/module/dmatest/parameters/run
[all …]
/linux/drivers/scsi/qedi/
H A Dqedi_fw_iscsi.h33 * @param task_params - Pointer to task parameters struct
34 * @param conn_params - Connection Parameters
35 * @param cmd_params - command specific parameters
36 * @param cmd_pdu_header - PDU Header Parameters
38 * @param dif_task_params - Pointer to DIF parameters struct
51 * @param task_params - Pointer to task parameters struct
52 * @param login_req_pdu_header - PDU Header Parameters
64 * @param task_params - Pointer to task parameters struct
65 * @param nop_out_pdu_header - PDU Header Parameters
77 * @param task_params - Pointer to task parameters struct
[all …]
/linux/include/xen/interface/
H A Devent_channel.h28 /* IN parameters */
30 /* OUT parameters */
45 /* IN parameters. */
48 /* OUT parameters. */
62 /* IN parameters. */
65 /* OUT parameters. */
77 /* IN parameters. */
81 /* OUT parameters. */
94 /* OUT parameters. */
105 /* IN parameters. */
[all …]
H A Dgrant_table.h282 /* IN parameters. */
287 /* OUT parameters. */
306 /* IN parameters. */
310 /* OUT parameters. */
325 /* IN parameters. */
328 /* OUT parameters. */
339 /* IN parameters. */
341 /* OUT parameters. */
356 /* IN parameters. */
360 /* OUT parameters. */
[all …]
/linux/Documentation/sound/designs/
H A Dtracepoints.rst13 and for processing of PCM hardware parameters. These tracepoints are available
24 Tracepoints for processing of PCM hardware parameters
33 substream. In this procedure, PCM hardware parameters are decided by
35 the PCM substream keeps the parameters.
37 The parameters are described in struct snd_pcm_hw_params. This
38 structure includes several types of parameters. Applications set preferable
39 value to these parameters, then execute ioctl(2) with SNDRV_PCM_IOCTL_HW_REFINE
41 set of parameters. The latter is used for an actual decision of the parameters.
47 convenient parameters or change their behaviour.
77 SNDRV_PCM_IOCTL_HW_PARAMS, this mask is ignored and all of parameters
[all …]
/linux/include/linux/
H A Dexecmem.h22 * permissions, alignment and other parameters for memory that can be used
25 * and let architectures define parameters for ranges suitable for
28 * @EXECMEM_DEFAULT: default parameters that would be used for types that
30 * @EXECMEM_MODULE_TEXT: parameters for module text sections
31 * @EXECMEM_KPROBES: parameters for kprobes
32 * @EXECMEM_FTRACE: parameters for ftrace
33 * @EXECMEM_BPF: parameters for BPF
34 * @EXECMEM_MODULE_DATA: parameters for module data sections
108 * struct execmem_info - architecture parameters for code allocations
110 * parameters for executable memory allocations. The ranges that are not
[all …]
H A Dzstd.h114 * struct zstd_compression_parameters - zstd compression parameters
133 * struct zstd_frame_parameters - zstd frame parameters
146 * struct zstd_parameters - zstd parameters
147 * @cParams: The compression parameters.
148 * @fParams: The frame parameters.
192 * @parameters: The compression parameters to be used.
194 * If multiple compression parameters might be used, the caller must call
195 * zstd_cctx_workspace_bound() for each set of parameters and use the maximum
201 size_t zstd_cctx_workspace_bound(const zstd_compression_parameters *parameters);
207 * @parameters: The compression parameters to be used.
[all …]
/linux/Documentation/userspace-api/media/v4l/
H A Dmetafmt-rkisp1.rst10 Configuration parameters
14 parameters for the ISP to the driver using the :c:type:`v4l2_meta_format`
17 There are two methods that allow to configure the ISP, the `fixed parameters`
18 configuration format and the `extensible parameters` configuration
23 Fixed parameters configuration format
26 When using the fixed configuration format, parameters are passed to the
39 use the extensible parameters method.
43 Extensible parameters configuration format
46 When using the extensible configuration format, parameters are passed to the
54 intends to configure. The extensible parameters format design allows developers
[all …]
H A Dmetafmt-pisp-be.rst13 configured by userspace by providing a buffer of configuration parameters
18 specifying two different sets of parameters by populating the members of
31 for example, LSC (Lens Shading Correction) or Denoise parameters would be common
37 Tile parameters
40 As the ISP processes images in tiles, each set of tiles parameters describe how
42 parameters consist of 160 bytes of data and to process a batch of tiles several
43 sets of tiles parameters are required.
45 Tiles parameters are passed to the ISP by populating the member of
H A Dvidioc-g-fmt.rst45 To query the current parameters applications set the ``type`` field of a
58 To change the current format parameters applications initialize the
61 :ref:`devices`. Good practice is to query the current parameters
62 first, and to modify only those parameters not suitable for the
65 checks and adjusts the parameters against hardware abilities. Drivers
68 parameters acceptable for both the application and driver. On success
71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
73 default parameters. However all V4L2 devices exchanging data with the
83 parameters, to learn about hardware limitations, without disabling I/O
118 - Raw VBI capture or output parameters. This is discussed in more
[all …]
H A Dmetafmt-intel-ipu3.rst25 The struct :c:type:`ipu3_uapi_4a_config` saves all configurable parameters.
43 Pipeline parameters
46 The pipeline parameters are passed to the "ipu3-imgu [01] parameters" metadata
50 Both 3A statistics and pipeline parameters described here are closely tied to
62 /* Accelerator cluster parameters */
65 /* ISP vector address space parameters */
70 /* ISP data memory (DMEM) parameters */
/linux/Documentation/firmware-guide/acpi/
H A Dmethod-tracing.rst30 /sys/module/acpi/parameters/debug_layer) and per-type level (known as
31 debug level, configured via /sys/module/acpi/parameters/debug_level).
46 # cd /sys/module/acpi/parameters
54 # cd /sys/module/acpi/parameters
58 # echo "method" > /sys/module/acpi/parameters/trace_state
63 # cd /sys/module/acpi/parameters
67 # echo "method-once" > /sys/module/acpi/parameters/trace_state
112 # cd /sys/module/acpi/parameters
120 # cd /sys/module/acpi/parameters
129 # cd /sys/module/acpi/parameters
[all …]
/linux/lib/zstd/
H A Dzstd_compress_module.c28 static size_t zstd_cctx_init(zstd_cctx *cctx, const zstd_parameters *parameters, in zstd_cctx_init() argument
36 cctx, ZSTD_c_windowLog, parameters->cParams.windowLog)); in zstd_cctx_init()
38 cctx, ZSTD_c_hashLog, parameters->cParams.hashLog)); in zstd_cctx_init()
40 cctx, ZSTD_c_chainLog, parameters->cParams.chainLog)); in zstd_cctx_init()
42 cctx, ZSTD_c_searchLog, parameters->cParams.searchLog)); in zstd_cctx_init()
44 cctx, ZSTD_c_minMatch, parameters->cParams.minMatch)); in zstd_cctx_init()
46 cctx, ZSTD_c_targetLength, parameters->cParams.targetLength)); in zstd_cctx_init()
48 cctx, ZSTD_c_strategy, parameters->cParams.strategy)); in zstd_cctx_init()
50 cctx, ZSTD_c_contentSizeFlag, parameters->fParams.contentSizeFlag)); in zstd_cctx_init()
52 cctx, ZSTD_c_checksumFlag, parameters->fParams.checksumFlag)); in zstd_cctx_init()
[all …]
/linux/Documentation/userspace-api/media/dvb/
H A Ddvb-frontend-parameters.rst6 frontend parameters
9 The kind of parameters passed to the frontend device for tuning depend
13 per-system parameters. However, as newer delivery systems required more
15 size would break the existing applications. So, those parameters were
18 ioctl's. The new API is flexible enough to add new parameters to
26 All kinds of parameters are combined as a union in the
54 QPSK parameters
71 QAM parameters
88 VSB parameters
103 OFDM parameters
H A Dfrontend-property-satellite-systems.rst15 The following parameters are valid for DVB-S:
40 Future implementations might add those two missing parameters:
52 In addition to all parameters valid for DVB-S, DVB-S2 supports the
53 following parameters:
74 In addition to all parameters valid for DVB-S, turbo code supports the
75 following parameters:
85 The following parameters are valid for ISDB-S:
/linux/drivers/media/platform/ti/omap3isp/
H A Disppreview.h59 * @busy: Bitmask of busy parameters (being updated or used)
60 * @update: Bitmask of the parameters to be updated
68 * @wbal: White Balance parameters.
69 * @blkadj: Black adjustment parameters.
70 * @rgb2rgb: RGB blending parameters.
71 * @csc: Color space conversion (RGB to YCbCr) parameters.
73 * @yclimit: YC limits parameters.
112 * @params.params : Active and shadow parameters sets
113 * @params.active: Bitmask of parameters active in set 0
114 * @params.lock: Parameters lock, protects params.active and params.shadow
/linux/fs/pstore/
H A DKconfig131 NOTE that, both Kconfig and module parameters can configure
132 pstore/blk, but module parameters have priority over Kconfig.
142 NOTE that, both Kconfig and module parameters can configure
143 pstore/blk, but module parameters have priority over Kconfig.
154 NOTE that, both Kconfig and module parameters can configure
155 pstore/blk, but module parameters have priority over Kconfig.
166 NOTE that, both Kconfig and module parameters can configure
167 pstore/blk, but module parameters have priority over Kconfig.
178 NOTE that, both Kconfig and module parameters can configure
179 pstore/blk, but module parameters have priority over Kconfig.
[all …]
/linux/Documentation/scsi/
H A Dscsi-parameters.rst4 SCSI Kernel Parameters
7 See Documentation/admin-guide/kernel-parameters.rst for general information on
8 specifying module parameters.
11 ``modinfo -p ${modulename}`` shows a current list of all parameters of a loadable
13 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
14 parameters may be changed at runtime by the command
15 ``echo -n ${value} > /sys/module/${modulename}/parameters/${parm}``.
104 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
/linux/drivers/clk/
H A Dclk-xgene.c633 struct xgene_dev_parameters *parameters, spinlock_t *lock) in xgene_register_clk() argument
653 apmclk->param = *parameters; in xgene_register_clk()
678 struct xgene_dev_parameters parameters; in xgene_devclk_init() local
686 parameters.csr_reg = NULL; in xgene_devclk_init()
687 parameters.divider_reg = NULL; in xgene_devclk_init()
704 parameters.divider_reg = map_res; in xgene_devclk_init()
706 parameters.csr_reg = map_res; in xgene_devclk_init()
708 if (of_property_read_u32(np, "csr-offset", &parameters.reg_csr_offset)) in xgene_devclk_init()
709 parameters.reg_csr_offset = 0; in xgene_devclk_init()
710 if (of_property_read_u32(np, "csr-mask", &parameters.reg_csr_mask)) in xgene_devclk_init()
[all …]
/linux/drivers/infiniband/hw/hfi1/
H A Dopfn.h32 * contains the parameters for negotiation and will be
39 * parameters, which will be sent to the requester QP once all
42 * keep a copy of the responder QP's parameters, and return a
43 * response packet with its own local parameters. The responder
45 * QP's parameters. After this exchange, each side has the parameters
46 * for both sides and therefore can select the right parameters
/linux/drivers/mtd/nand/raw/
H A Dnand_macronix.c54 if (!chip->parameters.supports_set_get_features || in macronix_nand_setup_read_retry()
56 chip->parameters.set_feature_list)) in macronix_nand_setup_read_retry()
104 struct nand_parameters *p = &chip->parameters; in macronix_nand_onfi_init()
178 if (!chip->parameters.supports_set_get_features) in macronix_nand_fix_broken_get_timings()
182 chip->parameters.model); in macronix_nand_fix_broken_get_timings()
186 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_fix_broken_get_timings()
188 bitmap_clear(chip->parameters.set_feature_list, in macronix_nand_fix_broken_get_timings()
235 bitmap_set(chip->parameters.get_feature_list, in macronix_nand_block_protection_support()
247 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_block_protection_support()
252 bitmap_set(chip->parameters.set_feature_list, in macronix_nand_block_protection_support()
[all …]
/linux/fs/vboxsf/
H A Dshfl_hostintf.h395 /** Create parameters buffer struct for SHFL_FN_CREATE call */
486 /** SHFL_FN_MAP_FOLDER Parameters structure. */
514 /* Number of parameters */
518 /** SHFL_FN_UNMAP_FOLDER Parameters structure. */
528 /* Number of parameters */
532 /** SHFL_FN_CREATE Parameters structure. */
554 /* Number of parameters */
558 /** SHFL_FN_CLOSE Parameters structure. */
574 /* Number of parameters */
578 /** SHFL_FN_READ Parameters structure. */
[all …]
/linux/net/ethtool/
H A Dmodule_fw.h8 * notifications parameters
20 * struct ethtool_module_fw_flash_params - module firmware flashing parameters
31 * parameters
33 * @params: Module firmware flashing parameters.
34 * @ntf_params: Module firmware flashing notification parameters.
49 * @fw_update: CMIS firmware update specific parameters.
/linux/include/uapi/linux/
H A Dgsmmux.h24 * struct gsm_config - n_gsm basic configuration parameters
27 * to retrieve and set the basic parameters of an n_gsm ldisc.
28 * struct gsm_config_ext can be used to configure extended ldisc parameters.
65 * struct gsm_netconfig - n_gsm network configuration parameters
93 * struct gsm_config_ext - n_gsm extended configuration parameters
96 * GSMIOC_SETCONF_EXT to retrieve and set the extended parameters of an
117 * struct gsm_dlci_config - n_gsm channel configuration parameters
120 * GSMIOC_SETCONF_DLCI to retrieve and set the channel specific parameters
/linux/Documentation/virt/kvm/devices/
H A Dvm.rst23 :Parameters: none
31 :Parameters: none
41 :Parameters: in attr->addr the address for the new limit of guest memory
73 :Parameters: address of buffer to store the machine related cpu data
97 :Parameters: address of buffer to store/set the processor related cpu
119 :Parameters: address of a buffer to load the feature list from.
132 :Parameters: address of a buffer to store/load the feature list from.
175 :Parameters: address of a buffer to load the subfunction blocks from.
198 :Parameters: address of a buffer to store/load the subfunction blocks from.
215 :Parameters: address of a buffer in user space to store the data (u8) to
[all …]

12345678910>>...112