Home
last modified time | relevance | path

Searched refs:parameters (Results 1 – 25 of 994) sorted by relevance

12345678910>>...40

/linux/lib/zstd/
H A Dzstd_compress_module.c35 cctx, ZSTD_c_windowLog, parameters->cParams.windowLog)); in zstd_cctx_init()
37 cctx, ZSTD_c_hashLog, parameters->cParams.hashLog)); in zstd_cctx_init()
39 cctx, ZSTD_c_chainLog, parameters->cParams.chainLog)); in zstd_cctx_init()
41 cctx, ZSTD_c_searchLog, parameters->cParams.searchLog)); in zstd_cctx_init()
43 cctx, ZSTD_c_minMatch, parameters->cParams.minMatch)); in zstd_cctx_init()
45 cctx, ZSTD_c_targetLength, parameters->cParams.targetLength)); in zstd_cctx_init()
47 cctx, ZSTD_c_strategy, parameters->cParams.strategy)); in zstd_cctx_init()
51 cctx, ZSTD_c_checksumFlag, parameters->fParams.checksumFlag)); in zstd_cctx_init()
53 cctx, ZSTD_c_dictIDFlag, !parameters->fParams.noDictIDFlag)); in zstd_cctx_init()
99 ZSTD_FORWARD_IF_ERR(zstd_cctx_init(cctx, parameters, src_size)); in zstd_compress_cctx()
[all …]
/linux/tools/testing/selftests/kvm/x86_64/
H A Dnx_huge_pages_test.sh11 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/driver-api/dmaengine/
H A Ddmatest.rst48 % echo 2000 > /sys/module/dmatest/parameters/timeout
49 % echo 1 > /sys/module/dmatest/parameters/iterations
51 % echo 1 > /sys/module/dmatest/parameters/run
65 % echo 1 > /sys/module/dmatest/parameters/run
90 % cat /sys/module/dmatest/parameters/run
108 % cat /sys/module/dmatest/parameters/wait
122 % grep -H . /sys/module/dmatest/parameters/*
162 % echo 1 > /sys/module/dmatest/parameters/run
182 % cat /sys/module/dmatest/parameters/channel
204 % cat /sys/module/dmatest/parameters/test_list
[all …]
/linux/drivers/clk/
H A Dclk-xgene.c646 apmclk->param = *parameters; in xgene_register_clk()
679 parameters.csr_reg = NULL; in xgene_devclk_init()
680 parameters.divider_reg = NULL; in xgene_devclk_init()
699 parameters.csr_reg = map_res; in xgene_devclk_init()
702 parameters.reg_csr_offset = 0; in xgene_devclk_init()
704 parameters.reg_csr_mask = 0xF; in xgene_devclk_init()
706 &parameters.reg_clk_offset)) in xgene_devclk_init()
709 parameters.reg_clk_mask = 0xF; in xgene_devclk_init()
733 if (parameters.csr_reg) in xgene_devclk_init()
734 iounmap(parameters.csr_reg); in xgene_devclk_init()
[all …]
/linux/drivers/mtd/nand/raw/
H A Dnand_macronix.c56 chip->parameters.set_feature_list)) in macronix_nand_setup_read_retry()
104 struct nand_parameters *p = &chip->parameters; in macronix_nand_onfi_init()
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()
252 bitmap_set(chip->parameters.set_feature_list, in macronix_nand_block_protection_support()
321 chip->parameters.model); in macronix_nand_deep_power_down_support()
466 chip->parameters.model) < 0) in macronix_nand_setup_otp()
472 bitmap_set(chip->parameters.get_feature_list, in macronix_nand_setup_otp()
[all …]
H A Dnand_onfi.c238 chip->parameters.model = kstrdup(p->model, GFP_KERNEL); in nand_onfi_detect()
239 if (!chip->parameters.model) { in nand_onfi_detect()
299 chip->parameters.supports_set_get_features = true; in nand_onfi_detect()
300 bitmap_set(chip->parameters.get_feature_list, in nand_onfi_detect()
302 bitmap_set(chip->parameters.set_feature_list, in nand_onfi_detect()
307 chip->parameters.supports_read_cache = true; in nand_onfi_detect()
326 chip->parameters.onfi = onfi; in nand_onfi_detect()
334 kfree(chip->parameters.model); in nand_onfi_detect()
/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/Documentation/userspace-api/media/v4l/
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 …]
H A Ddev-output.rst48 The output is determined by cropping and image format parameters. The
54 As usual these parameters are *not* reset at :c:func:`open()`
59 Cropping initialization at minimum requires to reset the parameters to
71 To request different parameters applications set the ``type`` field of a
77 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`
90 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
/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.
87 of parameters and execute ioctl(2) with SNDRV_PCM_IOCTL_HW_PARAMS to
[all …]
/linux/Documentation/firmware-guide/acpi/
H A Dmethod-tracing.rst46 # cd /sys/module/acpi/parameters
54 # cd /sys/module/acpi/parameters
63 # cd /sys/module/acpi/parameters
112 # cd /sys/module/acpi/parameters
120 # cd /sys/module/acpi/parameters
129 # cd /sys/module/acpi/parameters
138 # cd /sys/module/acpi/parameters
147 # cd /sys/module/acpi/parameters
154 be used as the boot parameters, for example::
164 parameters that are accessible at /sys/module/acpi/parameters/:
[all …]
H A Ddebug.rst22 debug_layer and debug_level files in /sys/module/acpi/parameters/ to control
34 to /sys/module/acpi/parameters/debug_layer.
38 Reading /sys/module/acpi/parameters/debug_layer shows the supported mask values::
68 to /sys/module/acpi/parameters/debug_level.
71 /sys/module/acpi/parameters/debug_level shows the supported mask values,
128 # echo 0x4 > /sys/module/acpi/parameters/debug_level
132 # cat /sys/module/acpi/parameters/debug_layer
/linux/Documentation/scsi/
H A Dscsi-parameters.rst7 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.)
H A Dindex.rst27 SCSI driver parameters
33 scsi-parameters
69 sd-parameters
/linux/drivers/scsi/smartpqi/
H A Dsmartpqi_sas_transport.c462 struct bmic_csmi_smp_passthru *parameters; in pqi_build_csmi_smp_passthru_buffer() local
481 parameters = &smp_buf->parameters; in pqi_build_csmi_smp_passthru_buffer()
482 parameters->phy_identifier = rphy->identify.phy_identifier; in pqi_build_csmi_smp_passthru_buffer()
483 parameters->port_identifier = 0; in pqi_build_csmi_smp_passthru_buffer()
484 parameters->connection_rate = 0; in pqi_build_csmi_smp_passthru_buffer()
486 &parameters->destination_sas_address); in pqi_build_csmi_smp_passthru_buffer()
491 put_unaligned_le32(req_size, &parameters->request_length); in pqi_build_csmi_smp_passthru_buffer()
492 put_unaligned_le32(resp_size, &parameters->response_length); in pqi_build_csmi_smp_passthru_buffer()
495 job->reply_payload.sg_cnt, &parameters->request, in pqi_build_csmi_smp_passthru_buffer()
506 job->reply_payload.sg_cnt, &smp_buf->parameters.response, in pqi_build_sas_smp_handler_reply()
[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
26 kernel command line (/proc/cmdline) and collects module parameters
45 Some kernel parameters take a list of CPUs as a value, e.g. isolcpus,
88 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
89 parameters may be changed at runtime by the command
197 Do not modify the syntax of boot loader parameters without extreme
[all …]
/linux/Documentation/i2c/
H A Dold-module-parameters.rst11 <linux/i2c.h> which created standard module parameters to let the user
13 parameters were known as ``probe`` (to let the driver probe for an extra
18 binding model, it became clear that these per-module parameters were no
24 Below is a mapping from the old module parameters to the new interface.
29 Old method (module parameters)::
42 Old method (module parameters)::
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-xen-blkback1 What: /sys/module/xen_blkback/parameters/max_buffer_pages
9 What: /sys/module/xen_blkback/parameters/max_persistent_grants
19 What: /sys/module/xen_blkback/parameters/persistent_grant_unused_seconds
29 What: /sys/module/xen_blkback/parameters/buffer_squeeze_duration_ms
39 What: /sys/module/xen_blkback/parameters/feature_persistent
/linux/Documentation/networking/devlink/
H A Docteontx2.rst13 The ``octeontx2 PF and VF`` drivers implement the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
29 The ``octeontx2 AF`` driver implements the following driver-specific parameters.
31 .. list-table:: Driver-specific parameters implemented
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,
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
H A Dnetdevsim.rst13 .. list-table:: Generic parameters implemented
21 parameters.
23 .. list-table:: Driver-specific parameters implemented
70 Rate nodes and their parameters are exposed in ``netdevsim`` debugfs in RO mode.
78 Same parameters are exposed for leaf objects in corresponding ports directories.
/linux/drivers/acpi/acpica/
H A Dnsxfeval.c247 info->parameters = ACPI_ALLOCATE_ZEROED(((acpi_size)info-> in ACPI_EXPORT_SYMBOL()
250 if (!info->parameters) { in ACPI_EXPORT_SYMBOL()
262 parameters[i]); in ACPI_EXPORT_SYMBOL()
268 info->parameters[info->param_count] = NULL; in ACPI_EXPORT_SYMBOL()
312 info->parameters = ACPI_ALLOCATE_ZEROED(((acpi_size) in ACPI_EXPORT_SYMBOL()
317 if (!info->parameters) { in ACPI_EXPORT_SYMBOL()
328 &info->parameters[i]); in ACPI_EXPORT_SYMBOL()
334 info->parameters[info->param_count] = NULL; in ACPI_EXPORT_SYMBOL()
439 if (info->parameters) { in ACPI_EXPORT_SYMBOL()
443 acpi_ut_delete_internal_object_list(info->parameters); in ACPI_EXPORT_SYMBOL()
/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 …]

12345678910>>...40