Home
last modified time | relevance | path

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

12345678910>>...172

/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/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/staging/media/atomisp/pci/isp/kernels/xnr/xnr_3.0/
H A Dia_css_xnr3_types.h11 * CSS-API header file for Extra Noise Reduction (XNR) parameters.
15 * \brief Scale of the XNR sigma parameters.
21 * \brief Scale of the XNR coring parameters.
33 * \brief XNR3 Sigma Parameters.
34 * \details Sigma parameters define the strength of the XNR filter.
37 * sigma parameters are fixed-point values between 0.0 and 1.0, scaled with
50 * \brief XNR3 Coring Parameters
51 * \details Coring parameters define the "coring" strength, which is a soft
54 * All coring parameters are fixed-point values between 0.0 and 1.0, scaled
65 * \brief XNR3 Blending Parameters
[all …]
/linux/drivers/hid/
H A Dhid-uclogic-params.c49 * uclogic_params_pen_hid_dbg() - Dump tablet interface pen parameters
50 * @hdev: The HID device the pen parameters describe.
51 * @pen: The pen parameters to dump.
53 * Dump tablet interface pen parameters with hid_dbg(). The dump is indented
83 * uclogic_params_frame_hid_dbg() - Dump tablet interface frame parameters
84 * @hdev: The HID device the pen parameters describe.
85 * @frame: The frame parameters to dump.
87 * Dump tablet interface frame parameters with hid_dbg(). The dump is
111 * uclogic_params_hid_dbg() - Dump tablet interface parameters
112 * @hdev: The HID device the parameters describe.
[all …]
/linux/drivers/staging/media/atomisp/pci/isp/kernels/hdr/
H A Dia_css_hdr_types.h14 * \brief HDR Irradiance Parameters
15 * \detail Currently HDR parameters are used only for testing purposes
35 * \brief HDR Deghosting Parameters
36 * \detail Currently HDR parameters are used only for testing purposes
43 * \brief HDR Exclusion Parameters
44 * \detail Currently HDR parameters are used only for testing purposes
51 * \brief HDR public parameters.
52 * \details Struct with all parameters for HDR that can be seet from
53 * the CSS API. Currently, only test parameters are defined.
56 struct ia_css_hdr_irradiance_params irradiance; /** HDR irradiance parameters */
[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 …]
/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/drivers/gpu/drm/amd/display/dc/inc/hw/
H A Dmpc.h352 * Parameters:
373 * Parameters:
403 * Parameters:
423 * Parameters:
438 * Parameters:
451 * Parameters:
472 * Parameters:
494 * Parameters:
524 * Parameters:
545 * Parameters:
[all …]
/linux/Documentation/admin-guide/
H A Dkernel-parameters.rst3 The kernel's command-line parameters
6 The following is a consolidated list of the kernel parameters as implemented
12 The kernel parses parameters from the kernel command line up to "``--``";
14 parameter gets passed to init: parameters with '=' go into init's
18 Module parameters can be specified in two ways: via the kernel command
24 Parameters for modules which are built into the kernel need to be
26 kernel command line (/proc/cmdline) and collects module parameters
31 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable
33 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
34 parameters may be changed at runtime by the command
[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/tools/testing/selftests/kvm/x86/
H A Dnx_huge_pages_test.sh5 # Makes use of root privileges to set up huge pages and KVM module parameters.
11 NX_HUGE_PAGES=$(cat /sys/module/kvm/parameters/nx_huge_pages)
12 NX_HUGE_PAGES_RECOVERY_RATIO=$(cat /sys/module/kvm/parameters/nx_huge_pages_recovery_ratio)
13 NX_HUGE_PAGES_RECOVERY_PERIOD=$(cat /sys/module/kvm/parameters/nx_huge_pages_recovery_period_ms)
40 sudo_echo 1 /sys/module/kvm/parameters/nx_huge_pages
41 sudo_echo 1 /sys/module/kvm/parameters/nx_huge_pages_recovery_ratio
42 sudo_echo 100 /sys/module/kvm/parameters/nx_huge_pages_recovery_period_ms
64 sudo_echo "$NX_HUGE_PAGES" /sys/module/kvm/parameters/nx_huge_pages
65 sudo_echo "$NX_HUGE_PAGES_RECOVERY_RATIO" /sys/module/kvm/parameters/nx_huge_pages_recovery_ratio
66 sudo_echo "$NX_HUGE_PAGES_RECOVERY_PERIOD" /sys/module/kvm/parameters/nx_huge_pages_recovery_period…
/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 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 */
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 …]
/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
/linux/include/uapi/linux/media/amlogic/
H A Dc3-isp-config.h139 * enum c3_isp_params_buffer_version - C3 ISP parameters block versioning
141 * @C3_ISP_PARAMS_BUFFER_V0: First version of C3 ISP parameters block
151 * The block type allows the driver to correctly interpret the parameters block
161 * @C3_ISP_PARAMS_BLOCK_PST_GAMMA: post gamma parameters
162 * @C3_ISP_PARAMS_BLOCK_CCM: Color correction matrix parameters
163 * @C3_ISP_PARAMS_BLOCK_CSC: Color space conversion parameters
164 * @C3_ISP_PARAMS_BLOCK_BLC: Black level correction parameters
186 * blocks. Each parameters block shall embed an instance of this structure type
195 * parameters block and is used by the driver for validation purposes. The
207 * Userspace is responsible for correctly populating the parameters block header
[all …]
/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/Documentation/networking/devlink/
H A Ddevlink-params.rst7 ``devlink`` provides capability for a driver to expose device parameters for low
12 This document describes a number of generic parameters that are supported
14 parameters. Each driver must document the specific parameters they support,
20 Parameters may be set in different configuration modes.
40 In order for ``driverinit`` parameters to take effect, the driver must
46 Generic configuration parameters
48 The following is a list of generic configuration parameters that drivers may
49 add. Use of generic parameters is preferred over each driver creating their
52 .. list-table:: List of generic parameters
/linux/drivers/clk/
H A Dclk-xgene.c626 struct xgene_dev_parameters *parameters, spinlock_t *lock) in xgene_register_clk() argument
646 apmclk->param = *parameters; in xgene_register_clk()
671 struct xgene_dev_parameters parameters; in xgene_devclk_init() local
679 parameters.csr_reg = NULL; in xgene_devclk_init()
680 parameters.divider_reg = NULL; in xgene_devclk_init()
697 parameters.divider_reg = map_res; in xgene_devclk_init()
699 parameters.csr_reg = map_res; in xgene_devclk_init()
701 if (of_property_read_u32(np, "csr-offset", &parameters.reg_csr_offset)) in xgene_devclk_init()
702 parameters.reg_csr_offset = 0; in xgene_devclk_init()
703 if (of_property_read_u32(np, "csr-mask", &parameters.reg_csr_mask)) in xgene_devclk_init()
[all …]

12345678910>>...172