Home
last modified time | relevance | path

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

12345678910>>...238

/linux/tools/testing/selftests/rcutorture/doc/
H A DTREE_RCU-kconfig.txt8 CONFIG_DEBUG_OBJECTS_RCU_HEAD -- Do one.
9 CONFIG_HZ_PERIODIC -- Do one.
11 CONFIG_NO_HZ_FULL -- Do two, one with partial CPU enablement.
15 CONFIG_RCU_BOOST -- one of PREEMPT_RCU.
17 CONFIG_RCU_FANOUT_LEAF -- Do one non-default.
18 CONFIG_RCU_NOCB_CPU -- Do three, one with no rcu_nocbs CPUs, one with
19 rcu_nocbs=0, and one with all rcu_nocbs CPUs.
21 CONFIG_SMP -- Need one !SMP for PREEMPT_RCU.
23 CONFIG_RCU_EQS_DEBUG -- Do at least one for CONFIG_NO_HZ_FULL and not.
25 RCU-bh: Do one with PREEMPT and one with !PREEMPT.
[all …]
/linux/Documentation/ABI/testing/
H A Ddebugfs-scmi-raw11 Each write to the entry causes one command request to be built
12 and sent while the replies are read back one message at time
29 Each write to the entry causes one command request to be built
30 and sent while the replies are read back one message at time
45 Each write to the entry causes one command request to be built
46 and sent while the replies are read back one message at time
65 Each write to the entry causes one command request to be built
66 and sent while the replies are read back one message at time
77 Each read gives back one message at time (receiving an EOF at
88 Each read gives back one message at time (receiving an EOF at
[all …]
/linux/Documentation/userspace-api/media/v4l/
H A Dtuner.rst14 Video input devices can have one or more tuners demodulating a RF
15 signal. Each tuner is associated with one or more video inputs,
22 Radio input devices have exactly one tuner with index zero, no video
35 current tuner, when there is more than one. The tuner is solely
39 device has one or more tuners.
45 Video output devices can have one or more modulators, that modulate a
47 set or video recorder. Each modulator is associated with one or more
55 Radio output devices have exactly one modulator with index zero, no
59 separate device nodes will have to be used for such hardware, one that
60 supports the tuner functionality and one that supports the modulator
[all …]
/linux/tools/testing/selftests/drivers/net/netdevsim/
H A Dtc-mq-visibility.sh51 # One real one
53 n_child_assert 4 "One real queue"
56 n_child_assert 2 "One real queue, one default"
59 n_child_assert 4 "One real queue, rest default"
61 # Remove real one
66 n_child_assert 3 "Deleting real one, replacing default one with pfifo"
69 n_child_assert 1 "Grafted, one"
/linux/drivers/tty/serial/
H A Dsc16is7xx.c329 struct sc16is7xx_one *one = to_sc16is7xx_one(port); in sc16is7xx_port_read() local
332 regmap_read(one->regmap, reg, &val); in sc16is7xx_port_read()
339 struct sc16is7xx_one *one = to_sc16is7xx_one(port); in sc16is7xx_port_write() local
341 regmap_write(one->regmap, reg, val); in sc16is7xx_port_write()
346 struct sc16is7xx_one *one = to_sc16is7xx_one(port); in sc16is7xx_fifo_read() local
348 regmap_noinc_read(one->regmap, SC16IS7XX_RHR_REG, rxbuf, rxlen); in sc16is7xx_fifo_read()
353 struct sc16is7xx_one *one = to_sc16is7xx_one(port); in sc16is7xx_fifo_write() local
362 regmap_noinc_write(one->regmap, SC16IS7XX_THR_REG, txbuf, to_send); in sc16is7xx_fifo_write()
368 struct sc16is7xx_one *one = to_sc16is7xx_one(port); in sc16is7xx_port_update() local
370 regmap_update_bits(one->regmap, reg, mask, val); in sc16is7xx_port_update()
[all …]
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A Duncore-interconnect.json398 …re per link and per direction, so for example the Tx direction could be in one state while Rx was …
407 …re per link and per direction, so for example the Tx direction could be in one state while Rx was …
416 …re per link and per direction, so for example the Tx direction could be in one state while Rx was …
532one talks about QPI 'speed' (for example, 8.0 GT/s), the 'transfers' here refer to 'fits'. Theref…
542one talks about QPI 'speed' (for example, 8.0 GT/s), the 'transfers' here refer to 'fits'. Theref…
552one talks about QPI 'speed' (for example, 8.0 GT/s), the 'transfers' here refer to 'fits'. Theref…
562one of three 'groups' that allow us to track flits. It includes filters for SNP, HOM, and DRS mes…
572one of three 'groups' that allow us to track flits. It includes filters for SNP, HOM, and DRS mes…
582one of three 'groups' that allow us to track flits. It includes filters for SNP, HOM, and DRS mes…
592one of three 'groups' that allow us to track flits. It includes filters for SNP, HOM, and DRS mes…
[all …]
H A Duncore-power.json16 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
25 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
34 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
43 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
52 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
61 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
70 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
79 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
160One can use all four counters with this event, so it is possible to track up to 4 configurable ban…
169One can use all four counters with this event, so it is possible to track up to 4 configurable ban…
[all …]
/linux/tools/testing/selftests/bpf/progs/
H A Dconnect4_prog.c109 int zero = 0, one = 1; in bind_to_device()
111 if (bpf_setsockopt(ctx, SOL_SOCKET, SO_KEEPALIVE, &one, sizeof(one)))
114 if (bpf_setsockopt(ctx, SOL_TCP, TCP_KEEPIDLE, &one, sizeof(one))) in set_keepalive() local
116 if (bpf_setsockopt(ctx, SOL_TCP, TCP_KEEPINTVL, &one, sizeof(one))) in set_keepalive()
118 if (bpf_setsockopt(ctx, SOL_TCP, TCP_KEEPCNT, &one, sizeof(one))) in set_keepalive()
120 if (bpf_setsockopt(ctx, SOL_TCP, TCP_SYNCNT, &one, sizeo in set_keepalive()
[all...]
/linux/include/linux/dma/
H A 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/Documentation/userspace-api/media/mediactl/
H A Dmedia-types.rst144 composing must have at least two sink pads and one source
152 must have at least one sink pad and one source pad. Read
161 encoding conversion must have at least one sink pad and one
170 processing must have one sink pad and one source pad. It uses
179 at least one sink pad and one source pad, and scale the
184 scaling can be supported in one direction only). Binning and
190 capable of statistics computation must have one sink pad and
191 one source pad. It computes statistics over the frames
197 compressing video frames. Must have one sink pad and at least
198 one source pad.
[all …]
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A Duncore-power.json16 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
25 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
34 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
43 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
52 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
61 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
70 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
79 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
88 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
97 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
[all …]
/linux/tools/testing/selftests/net/
H A Dtcp_port_share.c29 const int one = 1; variable
144 ASSERT_EQ(setsockopt(ln, SOL_SOCKET, SO_REUSEADDR, &one, sizeof(one)), 0); in TEST_F()
153 ASSERT_EQ(setsockopt(c1, SOL_IP, IP_BIND_ADDRESS_NO_PORT, &one, sizeof(one)), 0); in TEST_F()
165 ASSERT_EQ(setsockopt(pb, SOL_SOCKET, SO_REUSEADDR, &one, sizeof(one)), 0); in TEST_F()
173 ASSERT_EQ(setsockopt(c2, SOL_IP, IP_BIND_ADDRESS_NO_PORT, &one, sizeof(one)), 0); in TEST_F()
206 ASSERT_EQ(setsockopt(ln, SOL_SOCKET, SO_REUSEADDR, &one, sizeof(one)), 0); in TEST_F()
215 ASSERT_EQ(setsockopt(c1, SOL_IP, IP_BIND_ADDRESS_NO_PORT, &one, sizeof(one)), 0); in TEST_F()
226 ASSERT_EQ(setsockopt(c1, SOL_SOCKET, SO_REUSEADDR, &one, sizeof(one)), 0); in TEST_F()
234 ASSERT_EQ(setsockopt(pb, SOL_SOCKET, SO_REUSEADDR, &one, sizeof(one)), 0); in TEST_F()
244 ASSERT_EQ(setsockopt(c2, SOL_IP, IP_BIND_ADDRESS_NO_PORT, &one, sizeof(one)), 0); in TEST_F()
/linux/Documentation/devicetree/bindings/phy/
H A Drealtek,usb2phy.yaml16 support multiple XHCI controllers. One PHY device node maps to one XHCI
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
31 The controller#0 has one USB 2.0 PHY. The controller#1 includes two USB 2.0
39 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
47 Each xhci maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#0.
55 Each XHCI maps to one USB 2.0 PHY.
98 For one of the phys of RTD1619b SoC, the synchronous clock of the
H A Drealtek,usb3phy.yaml16 support multiple XHCI controllers. One PHY device node maps to one XHCI
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
31 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
39 Each xhci maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#0.
/linux/include/sound/sof/
H A Dchannel_map.h16 * \brief Channel map, specifies transformation of one-to-many or many-to-one.
18 * In case of one-to-many specifies how the output channels are computed out of
20 * in case of many-to-one specifies how a single target channel is computed
23 * Channel index specifies position of the channel in the stream on the 'one'
34 * one per each channel set in the mask (left to right, LS bit set in the
49 * More than one transformation per a single channel is allowed (in case
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dsprd,sc9860-pinctrl.yaml16 register contains several bit fields with one bit or several bits
19 driving level": One pin can output 3.0v or 1.8v, depending on the
22 to choose one function (like: UART0) for which system, since we
23 have several systems (AP/CP/CM4) on one SoC.).
27 as one generic configuration, and maybe it will add more strange
28 global configuration in future. Then we add one "sprd,control" to
32 Moreover we recognize every fields comprising one bit or several
33 bits in one global control register as one pin, thus we should
38 register definition, and each register described one pin is used
67 register definition, and each register described one pin is used to
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A Duncore-power.json16 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
25 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
34 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
43 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
52 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
61 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
70 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
79 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
88 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
97 …tion": "Number of cycles spent performing core C state transitions. There is one event per core.",
[all …]
/linux/drivers/mtd/spi-nor/
H A Dsfdp.h61 * two data bytes where bit 1 of the second byte is one.
63 * Writing only one byte to the status register has the side-effect of
65 * used if writing one byte to the status register does not modify
68 * one data byte where bit 6 is one.
71 * register 2 instruction 3Eh with one data byte where bit 7 is one.
75 * two data bytes where bit 1 of the second byte is one.
77 * In contrast to the 001b code, writing one byte to the status
82 * two data bytes where bit 1 of the second byte is one.
/linux/Documentation/devicetree/bindings/usb/
H A 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/Documentation/ABI/obsolete/
H A 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 …]
H A 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/Documentation/filesystems/
H A Dinotify.rst39 want: Users initialize inotify, once, and add n watches, requiring but one
57 versus just one. It is a lot messier in the kernel. A single, linear
72 Additionally, it _is_ possible to more than one instance and
73 juggle more than one queue and thus more than one associated fd. There
74 need not be a one-fd-per-process mapping; it is one-fd-per-queue and a
75 process can easily want more than one queue.
84 file descriptor-based one that allows basic file I/O and poll/select.
/linux/drivers/remoteproc/
H A Dpru_rproc.h19 * to host interrupts. Events can be mapped to channels in a one-to-one or
20 * many-to-one ratio (multiple events per channel), and channels can be
21 * mapped to host interrupts in a one-to-one or many-to-one ratio (multiple
/linux/arch/m68k/include/asm/
H A 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/Documentation/devicetree/bindings/iommu/
H A Dsamsung,sysmmu.yaml23 System MMUs are in many to one relation with peripheral devices, i.e. single
24 peripheral device might have multiple System MMUs (usually one for each bus
25 master), but one System MMU can handle transactions from only one peripheral
31 * MFC has one System MMU on its left and right bus.
32 * FIMD in Exynos5420 has one System MMU for window 0 and 4, the other system MMU
34 * M2M Scalers and G2D in Exynos5420 has one System MMU on the read channel and

12345678910>>...238