Home
last modified time | relevance | path

Searched full:one (Results 1 – 25 of 7234) sorted by relevance

12345678910>>...290

/Linux-v5.4/tools/testing/selftests/rcutorture/doc/
DTREE_RCU-kconfig.txt8 CONFIG_DEBUG_OBJECTS_RCU_HEAD -- Do one.
10 CONFIG_HZ_PERIODIC -- Do one.
12 CONFIG_NO_HZ_FULL -- Do two, one with partial CPU enablement.
16 CONFIG_RCU_BOOST -- one of PREEMPT_RCU.
18 CONFIG_RCU_FANOUT_LEAF -- Do one non-default.
19 CONFIG_RCU_FAST_NO_HZ -- Do one, but not with all nohz_full CPUs.
20 CONFIG_RCU_NOCB_CPU -- Do three, one with no rcu_nocbs CPUs, one with
21 rcu_nocbs=0, and one with all rcu_nocbs CPUs.
23 CONFIG_SMP -- Need one !SMP for PREEMPT_RCU.
25 CONFIG_RCU_EQS_DEBUG -- Do at least one for CONFIG_NO_HZ_FULL and not.
[all …]
/Linux-v5.4/lib/
Datomic64_test.c95 i, (i) + one, (i) + one); \
101 i, (i) - one, (i) - one); \
109 int one = 1; in test_atomic() local
115 TEST(, add, +=, -one); in test_atomic()
117 TEST(, sub, -=, -one); in test_atomic()
124 RETURN_FAMILY_TEST(, add_return, +=, -one); in test_atomic()
126 RETURN_FAMILY_TEST(, sub_return, -=, -one); in test_atomic()
129 FETCH_FAMILY_TEST(, fetch_add, +=, -one); in test_atomic()
131 FETCH_FAMILY_TEST(, fetch_sub, -=, -one); in test_atomic()
154 long long one = 1LL; in test_atomic64() local
[all …]
/Linux-v5.4/net/netfilter/ipset/
DKconfig32 This option adds the bitmap:ip set type support, by which one
41 This option adds the bitmap:ip,mac set type support, by which one
50 This option adds the bitmap:port set type support, by which one
59 This option adds the hash:ip set type support, by which one
69 This option adds the hash:ip,mark set type support, by which one
78 This option adds the hash:ip,port set type support, by which one
88 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
98 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
108 one can store IPv4/IPv6 address and MAC (ethernet address) pairs in a set.
117 one can store MAC (ethernet address) elements in a set.
[all …]
/Linux-v5.4/include/linux/iio/
Devents.h14 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
16 * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
17 * @direction: Direction of the event. One of enum iio_event_direction.
18 * @type: Type of the event. Should be one of enum iio_event_type.
34 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
36 * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
37 * @type: Type of the event. Should be one of enum iio_event_type.
38 * @direction: Direction of the event. One of enum iio_event_direction.
47 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
49 * @type: Type of the event. Should be one of enum iio_event_type.
[all …]
/Linux-v5.4/drivers/media/pci/cx18/
Dcx23418.h19 IN[0] - Task ID. This is one of the XPU_CMD_MASK_YYY where XPU is
23 ReturnCode - One of the ERR_SYS_... */
28 ReturnCode - One of the ERR_SYS_... */
68 ReturnCode - One of the ERR_DE_... */
84 ReturnCode - One of the ERR_CAPTURE_... */
90 ReturnCode - One of the ERR_CAPTURE_... */
95 ReturnCode - One of the ERR_CAPTURE_... */
100 ReturnCode - One of the ERR_CAPTURE_... */
117 ReturnCode - One of the ERR_CAPTURE_... */
123 ReturnCode - One of the ERR_CAPTURE_... */
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-driver-ufs18 Description: This file shows the device type. This is one of the UFS
26 Description: This file shows the device class. This is one of the UFS
34 Description: This file shows the UFS storage subclass. This is one of
43 This is one of the UFS device descriptor parameters.
51 Description: This file shows number of logical units. This is one of
60 This is one of the UFS device descriptor parameters.
69 enabled for boot. This is one of the UFS device descriptor
79 of the boot sequence. This is one of the UFS device descriptor
88 device initialization or hardware reset. This is one of
96 Description: This file shows the high priority lun. This is one of
[all …]
/Linux-v5.4/Documentation/media/uapi/v4l/
Dtuner.rst20 Video input devices can have one or more tuners demodulating a RF
21 signal. Each tuner is associated with one or more video inputs,
28 Radio input devices have exactly one tuner with index zero, no video
41 current tuner, when there is more than one. The tuner is solely
45 device has one or more tuners.
51 Video output devices can have one or more modulators, that modulate a
53 set or video recorder. Each modulator is associated with one or more
61 Radio output devices have exactly one modulator with index zero, no
65 separate device nodes will have to be used for such hardware, one that
66 supports the tuner functionality and one that supports the modulator
[all …]
Dpixfmt-compressed.rst45 The decoder expects one Access Unit per buffer.
46 The encoder generates one Access Unit per buffer.
78 one output and one capture buffer must be provided for use
123 Exactly one output and one capture buffer must be provided for use with
151 - VP8 compressed video frame. The encoder generates one
152 compressed frame per buffer, and the decoder requires one
164 Exactly one output and one capture buffer must be provided for use with
178 - VP9 compressed video frame. The encoder generates one
179 compressed frame per buffer, and the decoder requires one
186 The decoder expects one Access Unit per buffer.
[all …]
/Linux-v5.4/include/linux/dma/
Dsprd-dma.h16 * we can request 2 dma channels, one for source channel, and another one for
74 * and linklist mode. One transaction can contain several blocks, one block can
76 * configuration into one reserved memory, then DMA can fetch each DMA
89 * @SPRD_DMA_FRAG_INT: fragment done interrupt when one fragment request
91 * @SPRD_DMA_BLK_INT: block done interrupt when one block request is done.
92 * @SPRD_DMA_BLK_FRAG_INT: block and fragment interrupt when one fragment
93 * or one block request is done.
94 * @SPRD_DMA_TRANS_INT: tansaction done interrupt when one transaction
96 * @SPRD_DMA_TRANS_FRAG_INT: transaction and fragment interrupt when one
98 * @SPRD_DMA_TRANS_BLK_INT: transaction and block interrupt when one
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/pinctrl/
Dsprd,pinctrl.txt6 register contains several bit fields with one bit or several bits
9 driving level": One pin can output 3.0v or 1.8v, depending on the
12 to choose one function (like: UART0) for which system, since we
13 have several systems (AP/CP/CM4) on one SoC.).
17 as one generic configuration, and maybe it will add more strange
18 global configuration in future. Then we add one "sprd,control" to
22 Moreover we recognise every fields comprising one bit or several
23 bits in one global control register as one pin, thus we should
28 register definition, and each register described one pin is used
57 register definition, and each register described one pin is used to
/Linux-v5.4/drivers/gpu/drm/rcar-du/
Drcar_du_drv.c44 * R8A774[34] has one RGB output and one LVDS output
87 * R8A77470 has two RGB outputs, one LVDS output, and
88 * one (currently unsupported) analog video output
114 * R8A774A1 has one RGB output, one LVDS output and one HDMI
141 * R8A774C0 has one RGB output and two LVDS outputs
167 * R8A7779 has two RGB outputs and one (currently unsupported)
190 * R8A7790 has one RGB output, two LVDS outputs and one
218 * R8A779[13] has one RGB output, one LVDS output and one
260 * R8A7794 has two RGB outputs and one (currently unsupported)
283 * R8A7795 has one RGB output, two HDMI outputs and one
[all …]
/Linux-v5.4/Documentation/media/uapi/mediactl/
Dmedia-types.rst150 composing must have at least two sink pads and one source
158 must have at least one sink pad and one source pad. Read
167 encoding conversion must have at least one sink pad and one
176 processing must have one sink pad and one source pad. It uses
185 at least one sink pad and one source pad, and scale the
190 scaling can be supported in one direction only). Binning and
196 capable of statistics computation must have one sink pad and
197 one source pad. It computes statistics over the frames
203 compressing video frames. Must have one sink pad and at least
204 one source pad.
[all …]
/Linux-v5.4/drivers/usb/dwc3/
DKconfig65 Say 'Y' or 'M' here if you have one such device
72 Recent Exynos5 SoCs ship with one DesignWare Core USB3 IP inside,
73 say 'Y' or 'M' if you have one such device.
97 Say 'Y' or 'M' here if you have one such device
108 Say 'Y' or 'M' if you have one such device.
117 Say 'Y' or 'M' if you have one such device.
124 STMicroelectronics SoCs with one DesignWare Core USB3 IP
126 Say 'Y' or 'M' if you have one such device.
139 Say 'Y' or 'M' if you have one such device.
/Linux-v5.4/Documentation/devicetree/bindings/spi/
Dfsl-imx-cspi.txt6 - "fsl,imx1-cspi" for SPI compatible with the one integrated on i.MX1
7 - "fsl,imx21-cspi" for SPI compatible with the one integrated on i.MX21
8 - "fsl,imx27-cspi" for SPI compatible with the one integrated on i.MX27
9 - "fsl,imx31-cspi" for SPI compatible with the one integrated on i.MX31
10 - "fsl,imx35-cspi" for SPI compatible with the one integrated on i.MX35
11 - "fsl,imx51-ecspi" for SPI compatible with the one integrated on i.MX51
12 - "fsl,imx53-ecspi" for SPI compatible with the one integrated on i.MX53 and later Soc
13 - "fsl,imx8mq-ecspi" for SPI compatible with the one integrated on i.MX8M
/Linux-v5.4/Documentation/filesystems/
Dinotify.txt30 want: Users initialize inotify, once, and add n watches, requiring but one
48 versus just one. It is a lot messier in the kernel. A single, linear
63 Additionally, it _is_ possible to more than one instance and
64 juggle more than one queue and thus more than one associated fd. There
65 need not be a one-fd-per-process mapping; it is one-fd-per-queue and a
66 process can easily want more than one queue.
73 file descriptor-based one that allows basic file I/O and poll/select.
/Linux-v5.4/Documentation/devicetree/bindings/thermal/
Dthermal.txt30 control one or more internal sensors.
35 Size: one cell nodes with only one sensor, and at least 1 on nodes
64 Size: one cell to specify minimum and maximum cooling state used
80 Size: one cell
84 Size: one cell
112 Size: one cell The contribution is a ratio of the sum
125 thermal zone node must contain, apart from its own properties, one sub-node
126 containing trip nodes and one sub-node containing all the zone cooling maps.
131 Size: one cell
135 Size: one cell
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/usb/
Dgr-udc.txt15 - interrupts : Interrupt numbers for this device. Either one interrupt number
16 for all interrupts, or one for status related interrupts, one for IN
17 endpoint related interrupts and one for OUT endpoint related interrupts.
23 number. If the property is present it typically contains one entry for
29 number. If the property is present it typically contains one entry for
/Linux-v5.4/Documentation/devicetree/bindings/leds/
Dcommon.txt7 Many LED devices expose more than one current output that can be connected
8 to one or more discrete LED component. Since the arrangement of connections
19 - function: LED functon. Use one of the LED_FUNCTION_* prefixed definitions
21 If there is no matching LED_FUNCTION available, add a new one.
23 - color : Color of the LED. Use one of the LED_COLOR_ID_* prefixed definitions
25 If there is no matching LED_COLOR_ID available, add a new one.
27 - function-enumerator: Integer to be used when more than one instance
56 "pattern" - LED alters the brightness for the specified duration with one
61 - one-shot : two numbers specifying delay on and delay off (in ms),
89 In many cases LED can be related to more than one device
[all …]
/Linux-v5.4/tools/perf/pmu-events/arch/x86/tremontx/
Dfrontend.json4 …one or more bytes in an ICache Line and that cache line is not in the ICache (miss). The event st…
12 …"BriefDescription": "Counts requests to the Instruction Cache (ICache) for one or more bytes in a …
16 …r one or more bytes in an ICache Line. The event strives to count on a cache line basis, so that …
24 …"BriefDescription": "Counts requests to the Instruction Cache (ICache) for one or more bytes cache…
/Linux-v5.4/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-ryos4 Description: When written, this file lets one select which data from which
24 Description: When written, this file lets one set the default of all keys for
34 Description: When written, this file lets one set the function of the
44 Description: When written, this file lets one set the function of the macro
54 Description: When written, this file lets one set the function of the
64 Description: When written, this file lets one set the function of the
74 Description: When written, this file lets one set the function of the
84 Description: When written, this file lets one deactivate certain keys like
95 Description: When written, this file lets one set the backlight intensity for
106 Description: When written, this file lets one store macros with max 480
[all …]
Dsysfs-driver-hid-roccat-isku23 Description: When written, this file lets one deactivate certain keys like
34 Description: When written, this file lets one set the function of the
44 Description: When written, this file lets one set the function of the
54 Description: When written, this file lets one set the function of the
64 Description: When written, this file lets one set the function of the macro
74 Description: When written, this file lets one set the function of the media
84 Description: When written, this file lets one set the function of the
94 Description: When written, this file lets one set the time in secs since
102 Description: When written, this file lets one set the backlight intensity for
113 Description: When written, this file lets one store macros with max 500
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt13 System MMUs are in many to one relation with peripheral devices, i.e. single
14 peripheral device might have multiple System MMUs (usually one for each bus
15 master), but one System MMU can handle transactions from only one peripheral
21 * MFC has one System MMU on its left and right bus.
22 * FIMD in Exynos5420 has one System MMU for window 0 and 4, the other system MMU
24 * M2M Scalers and G2D in Exynos5420 has one System MMU on the read channel and
/Linux-v5.4/arch/m68k/include/asm/
Dmac_psc.h9 * The first seven DMA channels appear to be "one-shot" and are actually
10 * sets of two channels; one member is active while the other is being
12 * The one-shot channels are grouped together and are:
23 * to be closely tied and share one set of registers. They also seem to run
25 * not understood as there seems to be only one input and one output buffer
52 * One-shot DMA control registers
69 * You're supposed to use one channel while the other runs and
117 * bit 2 : Set to one to enable sound
122 * bit 6 : Set to one to enable pass-thru
126 * bit 7 : Set to one to activate the
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/serial/
Dfsl-lpuart.txt5 - "fsl,vf610-lpuart" for lpuart compatible with the one integrated
7 - "fsl,ls1021a-lpuart" for lpuart compatible with the one integrated
9 - "fsl,imx7ulp-lpuart" for lpuart compatible with the one integrated
11 - "fsl,imx8qxp-lpuart" for lpuart compatible with the one integrated
15 - clocks : phandle + clock specifier pairs, one for each entry in clock-names
22 - dmas: A list of two dma specifiers, one for each entry in dma-names.
/Linux-v5.4/Documentation/admin-guide/pm/
Dcpuidle.rst38 entity which appears to be fetching instructions that belong to one sequence
42 First, if the whole processor can only follow one sequence of instructions (one
47 least one program at a time. The cores need not be entirely independent of each
50 one program, those programs run mostly independently of each other at the same
56 except for one have been put into idle states at the "core level" and the
61 Finally, each core in a multi-core processor may be able to follow more than one
67 (or hyper-threads specifically on Intel hardware), that each can follow one
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
94 assigns it to one of the available CPUs to run and if there are no more runnable
96 code (from the instruction following the last one executed so far, possibly by
[all …]

12345678910>>...290