| /kernel/linux/linux-5.10/drivers/hid/ |
| D | hid-uclogic-params.c | 112 * uclogic_params_pen (tablet interface's pen input parameters).
115 * @pen: Pen input parameters to cleanup. Cannot be NULL.
125 * input and retrieve its parameters from the device, using v1 protocol.
127 * @pen: Pointer to the pen parameters to initialize (to be
129 * case of error, or if parameters are not found. Cannot be NULL.
130 * @pfound: Location for a flag which is set to true if the parameters
134 * parameters from. Cannot be NULL.
150 /* Pen report descriptor template parameters */ in uclogic_params_pen_init_v1()
161 * Read string descriptor containing pen input parameters. in uclogic_params_pen_init_v1()
169 "string descriptor with pen parameters not found, assuming not compatible\n"); in uclogic_params_pen_init_v1()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 38 % echo 2000 > /sys/module/dmatest/parameters/timeout
39 % echo 1 > /sys/module/dmatest/parameters/iterations
40 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
41 % echo 1 > /sys/module/dmatest/parameters/run
50 % echo 2000 > /sys/module/dmatest/parameters/timeout
51 % echo 1 > /sys/module/dmatest/parameters/iterations
52 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
53 % echo dma0chan1 > /sys/module/dmatest/parameters/channel
54 % echo dma0chan2 > /sys/module/dmatest/parameters/channel
55 % echo 1 > /sys/module/dmatest/parameters/run
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/qedi/ |
| D | qedi_fw_iscsi.h | 33 * @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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/xnr/xnr_3.0/ |
| D | ia_css_xnr3_types.h | 20 * CSS-API header file for Extra Noise Reduction (XNR) parameters.
24 * \brief Scale of the XNR sigma parameters.
30 * \brief Scale of the XNR coring parameters.
42 * \brief XNR3 Sigma Parameters.
43 * \details Sigma parameters define the strength of the XNR filter.
46 * sigma parameters are fixed-point values between 0.0 and 1.0, scaled with
59 * \brief XNR3 Coring Parameters
60 * \details Coring parameters define the "coring" strength, which is a soft
63 * All coring parameters are fixed-point values between 0.0 and 1.0, scaled
74 * \brief XNR3 Blending Parameters
[all …]
|
| /kernel/linux/linux-5.10/include/xen/interface/ |
| D | event_channel.h | 28 /* 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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/hdr/ |
| D | ia_css_hdr_types.h | 24 * \brief HDR Irradiance Parameters
25 * \detail Currently HDR parameters are used only for testing purposes
45 * \brief HDR Deghosting Parameters
46 * \detail Currently HDR parameters are used only for testing purposes
53 * \brief HDR Exclusion Parameters
54 * \detail Currently HDR parameters are used only for testing purposes
62 * \details Struct with all parameters for HDR that can be seet from
63 * the CSS API. Currenly, only test parameters are defined.
66 struct ia_css_hdr_irradiance_params irradiance; /** HDR irradiance parameters */
67 struct ia_css_hdr_deghost_params deghost; /** HDR deghosting parameters */
[all …]
|
| /kernel/linux/linux-5.10/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 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 …]
|
| /kernel/linux/linux-5.10/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
24 Parameters for modules which are built into the kernel need to be
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ia64/ |
| D | err_inject.rst | 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 …]
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/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:
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 19 device descriptor parameters. The full information about
28 device descriptor parameters. The full information about
37 the UFS device descriptor parameters. The full information
46 This is one of the UFS device descriptor parameters.
56 the UFS device descriptor parameters. The full information
65 This is one of the UFS device descriptor parameters.
76 parameters. The full information about the descriptor could
87 parameters. The full information about the descriptor could
97 the UFS device descriptor parameters. The full information
106 the UFS device descriptor parameters. The full information
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-params.rst | 7 ``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
|
| /kernel/linux/linux-5.10/fs/pstore/ |
| D | Kconfig | 218 NOTE that, both Kconfig and module parameters can configure
219 pstore/blk, but module parameters have priority over Kconfig.
229 NOTE that, both Kconfig and module parameters can configure
230 pstore/blk, but module parameters have priority over Kconfig.
241 NOTE that, both Kconfig and module parameters can configure
242 pstore/blk, but module parameters have priority over Kconfig.
253 NOTE that, both Kconfig and module parameters can configure
254 pstore/blk, but module parameters have priority over Kconfig.
265 NOTE that, both Kconfig and module parameters can configure
266 pstore/blk, but module parameters have priority over Kconfig.
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/platform/omap3isp/ |
| D | isppreview.h | 59 * @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
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | scsi-parameters.rst | 4 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}``.
107 st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-meta-intel-ipu3.rst | 25 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 */
|
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/clk/ |
| D | clk-xgene.c | 627 struct xgene_dev_parameters *parameters, spinlock_t *lock) in xgene_register_clk() argument
647 apmclk->param = *parameters; in xgene_register_clk()
672 struct xgene_dev_parameters parameters; in xgene_devclk_init() local
680 parameters.csr_reg = NULL; in xgene_devclk_init()
681 parameters.divider_reg = NULL; in xgene_devclk_init()
698 parameters.divider_reg = map_res; in xgene_devclk_init()
700 parameters.csr_reg = map_res; in xgene_devclk_init()
702 if (of_property_read_u32(np, "csr-offset", ¶meters.reg_csr_offset)) in xgene_devclk_init()
703 parameters.reg_csr_offset = 0; in xgene_devclk_init()
704 if (of_property_read_u32(np, "csr-mask", ¶meters.reg_csr_mask)) in xgene_devclk_init()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | psp-sev.h | 90 * struct sev_data_init - INIT command parameters
106 * struct sev_data_pek_csr - PEK_CSR command parameters
117 * struct sev_data_cert_import - PEK_CERT_IMPORT command parameters
133 * struct sev_data_download_firmware - DOWNLOAD_FIRMWARE command parameters
144 * struct sev_data_get_id - GET_ID command parameters
154 * struct sev_data_pdh_cert_export - PDH_CERT_EXPORT command parameters
170 * struct sev_data_decommission - DECOMMISSION command parameters
179 * struct sev_data_activate - ACTIVATE command parameters
190 * struct sev_data_deactivate - DEACTIVATE command parameters
199 * struct sev_data_guest_status - SEV GUEST_STATUS command parameters
[all …]
|
| /kernel/linux/linux-5.10/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 32 * 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
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/devices/ |
| D | vm.rst | 23 :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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/vt6655/ |
| D | mac.c | 48 * Parameters:
71 * Parameters:
94 * Parameters:
116 * Parameters:
138 * Parameters:
162 * Parameters:
191 * Parameters:
243 * Parameters:
274 * Parameters:
306 * Parameters:
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/nand/raw/ |
| D | nand_macronix.c | 43 if (!chip->parameters.supports_set_get_features || in macronix_nand_setup_read_retry()
45 chip->parameters.set_feature_list)) in macronix_nand_setup_read_retry()
93 struct nand_parameters *p = &chip->parameters; in macronix_nand_onfi_init()
168 if (!chip->parameters.supports_set_get_features) in macronix_nand_fix_broken_get_timings()
172 chip->parameters.model); in macronix_nand_fix_broken_get_timings()
176 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_fix_broken_get_timings()
178 bitmap_clear(chip->parameters.set_feature_list, in macronix_nand_fix_broken_get_timings()
225 bitmap_set(chip->parameters.get_feature_list, in macronix_nand_block_protection_support()
237 bitmap_clear(chip->parameters.get_feature_list, in macronix_nand_block_protection_support()
242 bitmap_set(chip->parameters.set_feature_list, in macronix_nand_block_protection_support()
[all …]
|