/Linux-v4.19/drivers/clk/ |
D | clk-xgene.c | 642 struct xgene_dev_parameters *parameters, spinlock_t *lock) in xgene_register_clk() argument 662 apmclk->param = *parameters; in xgene_register_clk() 687 struct xgene_dev_parameters parameters; in xgene_devclk_init() local 695 parameters.csr_reg = NULL; in xgene_devclk_init() 696 parameters.divider_reg = NULL; in xgene_devclk_init() 713 parameters.divider_reg = map_res; in xgene_devclk_init() 715 parameters.csr_reg = map_res; in xgene_devclk_init() 717 if (of_property_read_u32(np, "csr-offset", ¶meters.reg_csr_offset)) in xgene_devclk_init() 718 parameters.reg_csr_offset = 0; in xgene_devclk_init() 719 if (of_property_read_u32(np, "csr-mask", ¶meters.reg_csr_mask)) in xgene_devclk_init() [all …]
|
/Linux-v4.19/drivers/char/tpm/ |
D | tpm-sysfs.c | 28 u8 parameters[12]; member 79 out->parameters[0], out->parameters[1], in pubek_show() 80 out->parameters[2], out->parameters[3], in pubek_show() 81 out->parameters[4], out->parameters[5], in pubek_show() 82 out->parameters[6], out->parameters[7], in pubek_show() 83 out->parameters[8], out->parameters[9], in pubek_show() 84 out->parameters[10], out->parameters[11], in pubek_show()
|
/Linux-v4.19/Documentation/ia64/ |
D | err_inject.txt | 44 # err_type_info, err_struct_info: PAL parameters. 751 parameters_t parameters[MAX_TASK_NUM]={}; 785 parameters[num].cpu=cpu; 786 parameters[num].loop=loop; 787 parameters[num].interval= interval>MIN_INTERVAL 789 parameters[num].err_type_info=err_type_info_conf; 790 parameters[num].err_struct_info=err_struct_info_conf; 791 memcpy(parameters[num++].err_data_buffer, 799 parameters[0].cpu=line_para.cpu; 800 parameters[0].loop=line_para.loop; [all …]
|
/Linux-v4.19/Documentation/media/uapi/dvb/ |
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
|
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-v4.19/drivers/mtd/nand/raw/ |
D | nand_macronix.c | 38 if (!chip->parameters.supports_set_get_features) in macronix_nand_fix_broken_get_timings() 42 if (!strcmp(broken_get_timings[i], chip->parameters.model)) in macronix_nand_fix_broken_get_timings() 49 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_fix_broken_get_timings() 51 bitmap_clear(chip->parameters.set_feature_list, in macronix_nand_fix_broken_get_timings()
|
/Linux-v4.19/Documentation/driver-api/dmaengine/ |
D | dmatest.rst | 34 % echo dma0chan0 > /sys/module/dmatest/parameters/channel 35 % echo 2000 > /sys/module/dmatest/parameters/timeout 36 % echo 1 > /sys/module/dmatest/parameters/iterations 37 % echo 1 > /sys/module/dmatest/parameters/run 56 % cat /sys/module/dmatest/parameters/run 61 /sys/module/dmatest/parameters/wait waits for any running test to complete 74 % cat /sys/module/dmatest/parameters/wait 80 The module parameters that is supplied to the kernel command line will be used 82 re-run with the same or different parameters. For the details see the above 85 In both cases the module parameters are used as the actual values for the test [all …]
|
/Linux-v4.19/Documentation/sound/designs/ |
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 :c:type:`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-v4.19/Documentation/admin-guide/ |
D | kernel-parameters.rst | 3 The kernel's command-line parameters 6 The following is a consolidated list of the kernel parameters as 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, 74 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable 76 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these 77 parameters may be changed at runtime by the command [all …]
|
/Linux-v4.19/Documentation/isdn/ |
D | README.audio | 32 where xx is a two-character code and v are alphanumerical parameters. 40 AT+VIP Reset all audio parameters. 52 AT+VSD=x,y Set silence-detection parameters. 53 Possible parameters: 58 AT+VSD=? Report possible parameters. 59 AT+VSD? Show current parameters. 61 AT+VDD=x,y Set DTMF-detection parameters. 63 Possible parameters: 69 AT+VDD=? Report possible parameters. 70 AT+VDD? Show current parameters. [all …]
|
/Linux-v4.19/Documentation/acpi/ |
D | method-tracing.txt | 22 /sys/module/acpi/parameters/debug_layer) and per-type level (known as 23 debug level, configured via /sys/module/acpi/parameters/debug_level). 36 # cd /sys/module/acpi/parameters 42 # cd /sys/module/acpi/parameters 46 # echo "method" > /sys/module/acpi/parameters/trace_state 49 # cd /sys/module/acpi/parameters 53 # echo "method-once" > /sys/module/acpi/parameters/trace_state 92 # cd /sys/module/acpi/parameters 98 # cd /sys/module/acpi/parameters 105 # cd /sys/module/acpi/parameters [all …]
|
D | debug.txt | 20 debug_layer and debug_level files in /sys/module/acpi/parameters/ to control 32 to /sys/module/acpi/parameters/debug_layer. 35 include/acpi/acpi_drivers.h. Reading /sys/module/acpi/parameters/debug_layer 80 to /sys/module/acpi/parameters/debug_level. 83 /sys/module/acpi/parameters/debug_level shows the supported mask values, 144 # echo 0x4 > /sys/module/acpi/parameters/debug_level 148 # cat /sys/module/acpi/parameters/debug_layer
|
/Linux-v4.19/Documentation/scsi/ |
D | scsi-parameters.txt | 4 See Documentation/admin-guide/kernel-parameters.rst for general information on 5 specifying module parameters. 8 "modinfo -p ${modulename}" shows a current list of all parameters of a loadable 10 reveal their parameters in /sys/module/${modulename}/parameters/. Some of these 11 parameters may be changed at runtime by the command 12 "echo -n ${value} > /sys/module/${modulename}/parameters/${parm}". 108 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
|
/Linux-v4.19/Documentation/i2c/ |
D | old-module-parameters | 5 <linux/i2c.h> which created standard module parameters to let the user 7 parameters were known as "probe" (to let the driver probe for an extra 12 binding model, it became clear that these per-module parameters were no 17 Below is a mapping from the old module parameters to the new interface. 22 Old method (module parameters): 33 Old method (module parameters):
|
/Linux-v4.19/Documentation/ABI/testing/ |
D | sysfs-driver-ufs | 19 device descriptor parameters. The full information about 27 device descriptor parameters. The full information about 35 the UFS device descriptor parameters. The full information 43 This is one of the UFS device descriptor parameters. 52 the UFS device descriptor parameters. The full information 60 This is one of the UFS device descriptor parameters. 70 parameters. The full information about the descriptor could 80 parameters. The full information about the descriptor could 89 the UFS device descriptor parameters. The full information 97 the UFS device descriptor parameters. The full information [all …]
|
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
|
/Linux-v4.19/Documentation/media/uapi/v4l/ |
D | vidioc-g-fmt.rst | 43 To query the current parameters applications set the ``type`` field of a 56 To change the current format parameters applications initialize the 59 :ref:`devices`. Good practice is to query the current parameters 60 first, and to modify only those parameters not suitable for the 63 checks and adjusts the parameters against hardware abilities. Drivers 66 parameters acceptable for both the application and driver. On success 69 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple, 71 default parameters. However all V4L2 devices exchanging data with the 81 parameters, to learn about hardware limitations, without disabling I/O 122 - Raw VBI capture or output parameters. This is discussed in more [all …]
|
D | dev-output.rst | 50 The output is determined by cropping and image format parameters. The 56 As usual these parameters are *not* reset at :ref:`open() <func-open>` 61 Cropping initialization at minimum requires to reset the parameters to 73 To request different parameters applications set the ``type`` field of a 79 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 92 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
|
D | dev-capture.rst | 53 format parameters. The former select an area of the video picture to 58 As usual these parameters are *not* reset at :ref:`open() <func-open>` 63 Cropping initialization at minimum requires to reset the parameters to 76 To request different parameters applications set the ``type`` field of a 82 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 95 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does.
|
/Linux-v4.19/drivers/acpi/acpica/ |
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-v4.19/Documentation/fmc/ |
D | fmc-trivial.txt | 8 The module implements the generic FMC parameters, so it can program a 9 different gateware file in each card. The whole list of parameters it 14 Generic parameters. See mezzanine.txt
|
/Linux-v4.19/Documentation/ABI/stable/ |
D | sysfs-module | 15 /sys/module/MODULENAME/parameters 17 individual parameters of the module that are able to be 19 documentation as to the contents of these parameters and 26 stability of the different parameters.
|
/Linux-v4.19/Documentation/networking/ |
D | netconsole.txt | 52 parameters for the multiple agents separated by semicolons and the 84 parameters reconfigured at runtime from a configfs-based userspace interface. 85 [ Note that the parameters of netconsole targets that were specified/created 102 "1" to the "enabled" attribute (usually after setting parameters accordingly) 109 The interface exposes these parameters of a netconsole target to userspace: 121 The "enabled" attribute is also used to control whether the parameters of 122 a target can be updated or not -- you can modify the parameters of only 125 To update a target's parameters: 131 echo cb:a9:87:65:43:21 > remote_mac # update more parameters 177 from the config parameters passed to netconsole. [all …]
|
/Linux-v4.19/tools/testing/selftests/firmware/ |
D | fw_lib.sh | 106 echo -n "$FWPATH" >/sys/module/firmware_class/parameters/path 163 printf '\000' >/sys/module/firmware_class/parameters/path 165 echo -n "$OLD_FWPATH" >/sys/module/firmware_class/parameters/path
|
/Linux-v4.19/Documentation/device-mapper/ |
D | dm-flakey.txt | 16 Table parameters 21 Mandatory parameters: 28 Optional feature parameters: 29 If no feature parameters are present, during the periods of
|