| /Linux-v5.4/drivers/usb/serial/ |
| D | Kconfig | 16 supported, and on how to use them.
27 If you say Y here, it will be possible to use a USB to serial
41 kernel will automatically use the first USB to serial converter
49 Say Y here if you want to use the generic USB serial driver. Please
58 Say Y here to use the USB serial "simple" driver. This driver
81 Say Y here if you want to use USB AIRcable Bluetooth Dongle.
89 Say Y here if you want to use a ARK Micro 3116 USB to Serial
98 Say Y here if you want to use a Belkin USB Serial single port
108 Say Y here if you want to use a Winchiphead CH341 single port
118 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | macb.txt | 5 Use "cdns,at91rm9200-emac" Atmel at91rm9200 SoC.
6 Use "cdns,at91sam9260-macb" for Atmel at91sam9 SoCs.
7 Use "cdns,sam9x60-macb" for Microchip sam9x60 SoC.
8 Use "cdns,np4-macb" for NP4 SoC devices.
9 Use "cdns,at32ap7000-macb" for other 10/100 usage or use the generic form: "cdns,macb".
10 Use "cdns,pc302-gem" for Picochip picoXcell pc302 and later devices based on
12 Use "atmel,sama5d2-gem" for the GEM IP (10/100) available on Atmel sama5d2 SoCs.
13 Use "atmel,sama5d3-macb" for the 10/100Mbit IP available on Atmel sama5d3 SoCs.
14 Use "atmel,sama5d3-gem" for the Gigabit IP available on Atmel sama5d3 SoCs.
15 Use "atmel,sama5d4-gem" for the GEM IP (10/100) available on Atmel sama5d4 SoCs.
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | colorspaces-defs.rst | 34 two basic ways to do it: Divide the angular value by 2 (0-179), or use the
95 - Use the default transfer function as defined by the colorspace.
97 - Use the Rec. 709 transfer function.
99 - Use the sRGB transfer function.
101 - Use the opRGB transfer function.
103 - Use the SMPTE 240M transfer function.
105 - Do not use a transfer function (i.e. use linear RGB values).
107 - Use the DCI-P3 transfer function.
109 - Use the SMPTE 2084 transfer function. See :ref:`xf-smpte-2084`.
124 - Use the default Y'CbCr encoding as defined by the colorspace.
[all …]
|
| /Linux-v5.4/drivers/video/fbdev/via/ |
| D | tblDPASetting.c | 15 /* LCK/VCK < 30000000 will use this value */
18 /* 30000000 < LCK/VCK < 50000000 will use this value */
21 /* 50000000 < LCK/VCK < 70000000 will use this value */
24 /* 70000000 < LCK/VCK < 100000000 will use this value */
27 /* 100000000 < LCK/VCK < 15000000 will use this value */
30 /* 15000000 < LCK/VCK will use this value */
40 /* LCK/VCK < 30000000 will use this value */
42 /* 30000000 < LCK/VCK < 50000000 will use this value */
44 /* 50000000 < LCK/VCK < 70000000 will use this value */
46 /* 70000000 < LCK/VCK < 100000000 will use this value */
[all …]
|
| /Linux-v5.4/include/linux/platform_data/ |
| D | adp8870.h | 118 u8 l1_daylight_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
119 u8 l1_daylight_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
120 u8 l2_bright_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
121 u8 l2_bright_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
122 u8 l3_office_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
123 u8 l3_office_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
124 u8 l4_indoor_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
125 u8 l4_indor_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
126 u8 l5_dark_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
127 u8 l5_dark_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
[all …]
|
| /Linux-v5.4/drivers/gpu/drm/exynos/ |
| D | Kconfig | 22 Choose this option if you want to use Exynos FIMD for DRM.
27 Choose this option if you want to use Exynos5433 DECON for DRM.
33 Choose this option if you want to use Exynos DECON for DRM.
38 Choose this option if you want to use Exynos Mixer for DRM.
43 Choose this option if you want to use Exynos VIDI for DRM.
78 Choose this option if you want to use Exynos HDMI for DRM.
84 Choose this option if you want to use Exynos MIC for DRM.
93 Choose this option if you want to use Exynos G2D for DRM.
102 Choose this option if you want to use Exynos FIMC for DRM.
108 Choose this option if you want to use Exynos Rotator for DRM.
[all …]
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | boot-options.rst | 39 Do not opt-in to Local MCE delivery. Use legacy method
80 Use IO-APIC. Default
83 Don't use the IO-APIC.
86 Don't use the local APIC
89 Don't use the local APIC (alias for i386 compatibility)
109 Deprecated, use tsc=unstable instead.
112 Don't use the HPET timer.
131 Use the CPU reboot vector for warm reset
139 Use the keyboard controller. cold reset (default)
141 Use the ACPI RESET_REG in the FADT. If ACPI is not configured or
[all …]
|
| /Linux-v5.4/include/media/ |
| D | v4l2-mc.h | 37 * hardware should not use this routine, as it will not build the right graph.
42 * v4l_enable_media_source() - Hold media source for exclusive use
48 * media source is free for use. The enable_source handler is
74 * v4l_vb2q_enable_media_tuner - Hold media source for exclusive use
89 * v4l2_pipeline_pm_use - Update the use count of an entity
91 * @use: Use (1) or stop using (0) the entity
93 * Update the use count of all entities in the pipeline and power entities on or
96 * This function is intended to be called in video node open (use ==
97 * 1) and release (use == 0). It uses struct media_entity.use_count to
98 * track the power status. The use of this function should be paired
[all …]
|
| /Linux-v5.4/arch/mips/loongson32/ |
| D | Kconfig | 39 bool "Use PWM Timer for clockevent/clocksource"
54 bool "Use PWM Timer 0"
56 Use PWM Timer 0 as the default clockevent/clocksourcer.
59 bool "Use PWM Timer 1"
61 Use PWM Timer 1 as the default clockevent/clocksourcer.
64 bool "Use PWM Timer 2"
66 Use PWM Timer 2 as the default clockevent/clocksourcer.
69 bool "Use PWM Timer 3"
71 Use PWM Timer 3 as the default clockevent/clocksourcer.
|
| /Linux-v5.4/Documentation/core-api/ |
| D | memory-allocation.rst | 11 `alloc_pages`. It is also possible to use more specialized allocators,
14 Most of the memory allocation APIs use GFP flags to express how that
20 answer, although very likely you should use
41 many other allocations types can use ``GFP_KERNEL``. Note, that
46 handler, use ``GFP_NOWAIT``. This flag prevents direct reclaim and
51 will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``.
56 * Userspace allocations should use either of the ``GFP_USER``,
77 use new scope APIs described in
84 And even with hardware with restrictions it is preferable to use
90 The most straightforward way to allocate memory is to use a function
[all …]
|
| /Linux-v5.4/drivers/clk/qcom/ |
| D | Kconfig | 79 Say Y if you want to use peripheral devices such as UART, SPI,
95 Say Y if you want to use peripheral devices such as UART, SPI,
102 Say Y if you want to use peripheral devices such as UART, SPI,
110 Say Y if you want to use audio devices such as i2s, pcm,
117 Say Y if you want to use peripheral devices such as UART, SPI,
125 Say Y if you want to use peripheral devices such as UART, SPI,
133 Say Y if you want to use devices such as UART, SPI i2c, USB,
140 Say Y if you want to use peripheral devices such as UART, SPI,
148 Say Y if you want to use audio devices such as i2s, pcm,
155 Say Y if you want to use peripheral devices such as UART, SPI,
[all …]
|
| /Linux-v5.4/drivers/media/rc/ |
| D | Kconfig | 117 Windows Media Center Edition, which you would like to use with
134 remote control and you would like to use it with a raw IR
135 receiver, or if you wish to use an encoder to transmit this IR.
164 Say Y here if you want to use an X10 based USB remote control.
196 Say Y here if you want to use hisilicon hix5hd2 remote control.
208 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
220 Say Y here if you want to use a SoundGraph iMON IR Receiver,
232 Say Y here if you want to use a Windows Media Center Edition
268 Say Y if you want to use the IR remote receiver available
279 Say Y if you want to use the IR remote receiver available
[all …]
|
| /Linux-v5.4/Documentation/arm64/ |
| D | acpi_object_usage.rst | 47 Optional, not currently supported, with no real use-case for an
178 ARM-specific error sources have been defined; please use those or the
180 Bridge), or use type 9 (Generic Hardware Error Source). Firmware first
221 descriptions and power states on ARM platforms should use the DSDT
273 use. Since these are not meant to be of general use but are limited
274 to very specific end users, they are not recommended for use and are
281 Recommend for use on arm64; use of PCC is recommended when using CPPC
357 for use with devices that can be added to a running system, but can
392 Optional, not currently supported. No known use case for arm64,
457 _CID 6.1.2 Use as needed, see also _HID.
[all …]
|
| /Linux-v5.4/drivers/input/keyboard/ |
| D | Kconfig | 45 Say Y here if you want to use a ADP5588/87 attached to your
55 Say Y here if you want to use a ADP5585/ADP5589 attached to your
111 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
122 bool "Use HP keyboard scancodes"
126 Say Y here if you have a PA-RISC machine and want to use an AT or
130 Say N if you use a standard keyboard.
133 bool "Use PrecisionBook keyboard scancodes"
137 If you have an RDI PrecisionBook, say Y here if you want to use its
151 If you say N here, and use the PrecisionBook keyboard, then each key
155 If you say Y here, and use an external keyboard, then each key in the
[all …]
|
| /Linux-v5.4/drivers/w1/slaves/ |
| D | Kconfig | 23 Say Y or M here if you want to use a DS2405 1-wire
31 Say Y here if you want to use a 1-wire
47 Say Y here if you want to use a 1-wire
54 Say Y or M here if you want to use a 1-wire
66 Say Y here if you want to use a 1-wire
72 Say Y here if you want to use a 1-wire
80 Say Y here if you want to use a 1-wire
86 Say Y here if you want to use a 1-wire
101 Say Y here if you want to use a 1-wire
108 Say Y here if you want to use a 1-wire
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | atmel-usart.txt | 7 For the dbgu UART, use "atmel,<chip>-dbgu", "atmel,<chip>-usart"
33 - atmel,use-dma-rx: use of PDC or DMA for receiving data
34 - atmel,use-dma-tx: use of PDC or DMA for transmitting data
36 It will use specified PIO instead of the peripheral function pin for the USART feature.
47 - use PDC:
54 atmel,use-dma-rx;
55 atmel,use-dma-tx;
64 - use DMA:
71 atmel,use-dma-rx;
72 atmel,use-dma-tx;
|
| /Linux-v5.4/Documentation/driver-api/pci/ |
| D | p2pdma.rst | 23 The second issue is that to make use of existing interfaces in Linux,
38 * Client - A driver which makes use of a resource by setting up a
51 to be used directly (client) and it can also make use of the CMB as
62 then the NVMe Target could use the RNIC's memory instead of the CMB
63 in cases where the NVMe cards in use do not have CMB support.
75 any orchestrator drivers to find and use the memory. When marked in
87 routine to use the mapping function :c:func:`pci_p2pdma_map_sg()` instead
91 The client may also, optionally, make use of
92 :c:func:`is_pci_p2pdma_page()` to determine when to use the P2P mapping
93 functions and when to use the regular mapping functions. In some
[all …]
|
| /Linux-v5.4/arch/ia64/include/uapi/asm/ |
| D | perfmon.h | 21 #define PFM_DESTROY_CONTEXT 0x09 /* obsolete use close() */
47 #define PFM_SETFL_EXCL_IDLE 0x01 /* exclude idle task (syswide only) XXX: DO NOT USE YET */
73 pfm_uuid_t ctx_smpl_buf_id; /* which buffer format to use (if needed) */
76 unsigned short ctx_reserved1; /* for future use */
79 unsigned long ctx_reserved2[11];/* for future use */
88 unsigned short reg_reserved1; /* for future use */
104 unsigned long reg_reserved2[3]; /* for future use */
110 unsigned short dbreg_reserved1; /* for future use */
113 unsigned long dbreg_reserved2[1]; /* for future use */
118 unsigned int ft_reserved; /* reserved for future use */
[all …]
|
| /Linux-v5.4/arch/m68k/include/asm/ |
| D | MC68VZ328.h | 380 #define PB_CSB0 0x01 /* Use CSB0 as PB[0] */
381 #define PB_CSB1 0x02 /* Use CSB1 as PB[1] */
382 #define PB_CSC0_RAS0 0x04 /* Use CSC0/RAS0 as PB[2] */
383 #define PB_CSC1_RAS1 0x08 /* Use CSC1/RAS1 as PB[3] */
384 #define PB_CSD0_CAS0 0x10 /* Use CSD0/CAS0 as PB[4] */
385 #define PB_CSD1_CAS1 0x20 /* Use CSD1/CAS1 as PB[5] */
386 #define PB_TIN_TOUT 0x40 /* Use TIN/TOUT as PB[6] */
387 #define PB_PWMO 0x80 /* Use PWMO as PB[7] */
404 #define PC_LD0 0x01 /* Use LD0 as PC[0] */
405 #define PC_LD1 0x02 /* Use LD1 as PC[1] */
[all …]
|
| /Linux-v5.4/arch/nios2/include/asm/ |
| D | asm-macros.h | 16 * You cannnot use the same register for reg1 & reg2.
36 * It is safe to use the same register for reg1 & reg2.
55 * It is safe to use the same register for reg1 & reg2.
75 * It is safe to use the same register for reg1 & reg2.
94 * It is safe to use the same register for reg1 & reg2.
106 * It is safe to use the same register for reg1 & reg2.
118 * It is NOT safe to use the same register for reg1 & reg2.
139 * It is NOT safe to use the same register for reg1 & reg2.
160 * It is NOT safe to use the same register for reg1 & reg2.
182 * It is NOT safe to use the same register for reg1 & reg2.
[all …]
|
| /Linux-v5.4/drivers/tty/serial/ |
| D | Kconfig | 38 Say Y here if you wish to use an AMBA PrimeCell UART as the system
66 Say Y here if you wish to use an AMBA PrimeCell UART as the system
122 If you say Y here, it will be possible to use a serial port as the
144 Say Y here if you wish to use an on-chip UART on a Atmel
154 Say Y here if you wish to use the PDC to do DMA transfers to
156 actually use DMA transfers, make sure that the use_dma_tx
162 this matters don't use DMA.
176 To use this, you should create suitable ttyATn device nodes in
185 This special driver allows you to temporary use NMI debugger port
196 use raw console.
[all …]
|
| /Linux-v5.4/Documentation/vm/ |
| D | swap_numa.rst | 8 information, we can make use of this information to decide which swap
9 device to use in get_swap_pages() to get better performance.
12 How to use this feature
16 use of automatically binding, there is no need to manipulate priority settings
24 Then node 0 will use the two swap devices in the order of swapA then swapB and
25 node 1 will use the two swap devices in the order of swapB then swapA. Note
40 Then node 0 will use them in the order of::
46 node 1 will use them in the order of::
50 node 2 will use them in the order of::
57 node 3 will use them in the order of::
[all …]
|
| /Linux-v5.4/Documentation/process/ |
| D | email-clients.rst | 9 These days most developers use ``git send-email`` instead of regular
11 end, maintainers use ``git am`` to apply the patches.
51 Don't use PGP/GPG signatures in mail that contains patches.
90 Works. Some people use this successfully for patches.
92 To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`)
103 Some people use this successfully for patches.
109 Then use:
119 Some people use Kmail successfully for patches.
158 :menuselection:`save as`. You can use the whole email unmodified as a patch
176 Plenty of Linux developers use ``mutt``, so it must work pretty well.
[all …]
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/tc-tests/actions/ |
| D | ife.json | 41 "cmdUnderTest": "$TC actions add action ife encode use mark 10 pipe index 2",
44 … "matchPattern": "action order [0-9]*: ife encode action pipe.*type 0[xX]ED3E.*use mark.*index 2",
89 "cmdUnderTest": "$TC actions add action ife encode use mark 789 drop index 2",
92 …"matchPattern": "action order [0-9]*: ife encode action drop.*type 0[xX]ED3E.*use mark 789.*index …
113 "cmdUnderTest": "$TC actions add action ife encode use mark 656768 reclassify index 2",
116 …"matchPattern": "action order [0-9]*: ife encode action reclassify.*type 0[xX]ED3E.*use mark 65676…
137 "cmdUnderTest": "$TC actions add action ife encode use mark 65 jump 1 index 2",
140 …"matchPattern": "action order [0-9]*: ife encode action jump 1.*type 0[xX]ED3E.*use mark 65.*index…
161 "cmdUnderTest": "$TC actions add action ife encode use mark 4294967295 reclassify index 90",
164 …"matchPattern": "action order [0-9]*: ife encode action reclassify.*type 0[xX]ED3E.*use mark 42949…
[all …]
|
| /Linux-v5.4/drivers/mtd/ |
| D | Kconfig | 24 test. Do not use these tests unless you really know what you do.
44 as block devices, it is possible to use MTD devices which are based
50 (although JFFS and JFFS2 don't actually use any of the functionality
58 You do not need this option for use with the DiskOnChip devices. For
70 You do not need this option for use with the DiskOnChip devices. For
85 legal - in the USA you are only permitted to use this on PCMCIA
88 not use it.
102 legal - in the USA you are only permitted to use this on DiskOnChip
105 not use it.
127 legal - in the USA you are only permitted to use this on DiskOnChip
[all …]
|
