| /linux/lib/zstd/ |
| H A D | zstd_compress_module.c | 28 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/driver-api/dmaengine/ |
| H A D | dmatest.rst | 48 % 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/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-rkisp1.rst | 11 Configuration parameters 15 parameters for the ISP to the driver using the :c:type:`v4l2_meta_format` 18 There are two methods that allow to configure the ISP, the `fixed parameters` 19 configuration format and the `extensible parameters` configuration 24 Fixed parameters configuration format 27 When using the fixed configuration format, parameters are passed to the 40 use the extensible parameters method. 44 Extensible parameters configuration format 47 When using the extensible configuration format, parameters are passed to the 55 intends to configure. The extensible parameters format design allows developers [all …]
|
| H A D | metafmt-intel-ipu3.rst | 26 The struct :c:type:`ipu3_uapi_4a_config` saves all configurable parameters. 44 Pipeline parameters 47 The pipeline parameters are passed to the "ipu3-imgu [01] parameters" metadata 51 Both 3A statistics and pipeline parameters described here are closely tied to 63 /* Accelerator cluster parameters */ 66 /* ISP vector address space parameters */ 71 /* ISP data memory (DMEM) parameters */
|
| H A D | metafmt-pisp-be.rst | 14 configured by userspace by providing a buffer of configuration parameters 19 specifying two different sets of parameters by populating the members of 32 for example, LSC (Lens Shading Correction) or Denoise parameters would be common 38 Tile parameters 41 As the ISP processes images in tiles, each set of tiles parameters describe how 43 parameters consist of 160 bytes of data and to process a batch of tiles several 44 sets of tiles parameters are required. 46 Tiles parameters are passed to the ISP by populating the member of
|
| H A D | vidioc-g-fmt.rst | 45 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 D | dev-output.rst | 48 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.
|
| H A D | dev-capture.rst | 51 format parameters. The former select an area of the video picture to 56 As usual these parameters are *not* reset at :c:func:`open()` 61 Cropping initialization at minimum requires to reset the parameters to 74 To request different parameters applications set the ``type`` field of a 80 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 93 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
|
| /linux/drivers/clk/ |
| H A D | clk-xgene.c | 633 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", ¶meters.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", ¶meters.reg_csr_mask)) in xgene_devclk_init() [all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.rst | 5 The kernel's command-line parameters 8 The following is a consolidated list of the kernel parameters as implemented 14 The kernel parses parameters from the kernel command line up to "``--``"; 16 parameter gets passed to init: parameters with '=' go into init's 20 Module parameters can be specified in two ways: via the kernel command 28 kernel command line (/proc/cmdline) and collects module parameters 33 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable 35 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these 36 parameters may be changed at runtime by the command 37 ``echo -n ${value} > /sys/module/${modulename}/parameters/${parm}``. [all …]
|
| /linux/drivers/mtd/nand/raw/ |
| H A D | nand_macronix.c | 54 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 …]
|
| H A D | nand_onfi.c | 238 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 D | dvb-frontend-parameters.rst | 6 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 D | frontend-property-satellite-systems.rst | 15 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/sound/designs/ |
| H A D | tracepoints.rst | 13 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/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 30 /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 …]
|
| H A D | debug.rst | 22 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 D | scsi-parameters.rst | 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.)
|
| H A D | index.rst | 27 SCSI driver parameters 33 scsi-parameters 69 sd-parameters
|
| /linux/drivers/scsi/smartpqi/ |
| H A D | smartpqi_sas_transport.c | 462 struct bmic_csmi_smp_passthru *parameters; in pqi_build_csmi_smp_passthru_buffer() local 479 put_unaligned_le32(sizeof(smp_buf->parameters), &ioctl_header->length); in pqi_build_csmi_smp_passthru_buffer() 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 ¶meters->destination_sas_address); in pqi_build_csmi_smp_passthru_buffer() 491 put_unaligned_le32(req_size, ¶meters->request_length); in pqi_build_csmi_smp_passthru_buffer() 492 put_unaligned_le32(resp_size, ¶meters->response_length); in pqi_build_csmi_smp_passthru_buffer() 495 job->reply_payload.sg_cnt, ¶meters->request, in pqi_build_csmi_smp_passthru_buffer() [all …]
|
| /linux/Documentation/i2c/ |
| H A D | old-module-parameters.rst | 11 <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 D | sysfs-driver-xen-blkback | 1 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/fs/pstore/ |
| H A D | Kconfig | 131 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/drivers/acpi/acpica/ |
| H A D | nsxfeval.c | 247 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/Documentation/networking/devlink/ |
| H A D | netdevsim.rst | 13 .. 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.
|