Home
last modified time | relevance | path

Searched full:stopped (Results 1 – 25 of 114) sorted by relevance

12345

/Documentation/watchdog/
Dwatchdog-parameters.rst33 Watchdog cannot be stopped once started
46 Watchdog cannot be stopped once started
55 Watchdog cannot be stopped once started
67 Watchdog cannot be stopped once started
94 Watchdog cannot be stopped once started
103 Watchdog cannot be stopped once started
112 Watchdog cannot be stopped once started
147 Watchdog cannot be stopped once started
162 Watchdog cannot be stopped once started
168 Watchdog cannot be stopped once started
[all …]
Dmlx-wdt.rst52 it can't be stopped.
/Documentation/accounting/
Dcgroupstats.rst29 sleeping 1, blocked 0, running 1, stopped 0, uninterruptible 0
31 sleeping 155, blocked 0, running 1, stopped 0, uninterruptible 2
/Documentation/driver-api/dmaengine/
Dpxa_dma.rst28 a check of the DMA channel reports a "stopped channel", the transfer should
30 know if a channel is in running or stopped state.
94 If while new_link was created the DMA channel stopped, it is _not_
104 - then hot-chaining cannot happen, as the channel must be stopped, the
187 It should be noted that after tx3 is completed, the channel is stopped, and
Dclient.rst88 operation is explicitly stopped.
311 This causes all activity for the DMA channel to be stopped, and may
318 stopped or until any running complete callbacks have finished. But it is
/Documentation/networking/
Dcan_ucan_protocol.rst174 stopped SET_BITTIMING stopped
175 stopped START started
176 started STOP or RESET stopped
177 stopped STOP or RESET stopped
Dopenvswitch.rst52 headers but userspace stopped at the Ethernet type (because it
59 the kernel stopped at the Ethernet type, then userspace can
168 the 802.1Q TPID (0x8100) as the Ethertype then stopped parsing the
/Documentation/driver-api/media/drivers/
Dpxa_camera.rst20 a) QCI stopped
21 Initially, the QCI interface is stopped.
84 - "DMA: stop" means all 3 DMA channels are stopped
103 On the DMA irq of the last videobuffer, the QCI is stopped.
170 - Videobuffer3 capture is not scheduled on DMA chain (as it stopped !!!)
/Documentation/filesystems/spufs/
Dspu_run.rst66 SPU was stopped by stop-and-signal.
69 SPU was stopped by halt.
/Documentation/tools/rtla/
Dcommon_osnoise_options.rst31 Save the stopped trace to [*file|osnoise_trace.txt*].
Dcommon_timerlat_options.rst27 Save the stopped trace to [*file|timerlat_trace.txt*].
/Documentation/userspace-api/media/dvb/
Ddmx-start.rst61 Make sure that these filters are stopped before starting this
Ddmx-set-pes-filter.rst60 Make sure that these filters are stopped before starting this
Ddmx-set-filter.rst41 stopped after the first section is received, and whether the filtering
Ddmx-fwrite.rst66 front- end. Make sure that these filters are stopped and that the
/Documentation/userspace-api/media/v4l/
Ddev-encoder.rst60 node [shape = circle, label="Stopped"] Stopped;
71 Encoding -> Stopped [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
74 Drain -> Stopped [ label = "All CAPTURE\nbuffers dequeued\nor\nVIDIOC_STREAMOFF(OUTPUT)" ];
80 Stopped -> Encoding [ label = "V4L2_ENC_CMD_START\nor\nVIDIOC_STREAMON(OUTPUT)" ];
81 Stopped -> Reset [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
547 -EBUSY error code, the ``CAPTURE`` queue needs to be stopped for the
619 dequeued and the last ``CAPTURE`` buffer is dequeued, the encoder is stopped
Ddev-decoder.rst180 node [shape = circle, label="Stopped"] Stopped;
190 CaptureSetup -> Stopped [ label = "CAPTURE\nbuffers\nready" ];
196 Decoding -> Stopped [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
204 Drain -> Stopped [ label = "All CAPTURE\nbuffers dequeued\nor\nVIDIOC_STREAMOFF(CAPTURE)" ];
210 Stopped -> Decoding [ label = "V4L2_DEC_CMD_START\nor\nVIDIOC_STREAMON(CAPTURE)" ];
211 Stopped -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
975 explicit `Drain` sequence. The decoder is stopped after it completes.
1064 stopped and it will accept, but not process, any newly queued ``OUTPUT``
Dvidioc-decoder-cmd.rst163 - Stop the decoder. When the decoder is already stopped, this
166 the picture to black after it stopped decoding. Otherwise the last
/Documentation/input/
Dnotifier.rst26 order to "eat" the event: the notify loop is stopped and the keyboard event is
/Documentation/admin-guide/perf/
Dthunderx2-pmu.rst15 can be started and stopped individually. None of the counters support an
/Documentation/admin-guide/pm/
Dcpuidle.rst70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
165 tick can be `stopped by the idle loop <idle-cpus-and-tick_>`_. Available
233 which is expensive. On the other hand, if the tick is stopped and the wakeup
238 governor will select a relatively deep idle state, so the tick should be stopped
243 stopped already (in one of the previous iterations of the loop), it is better
251 ignored by the idle loop code and the tick is never stopped.
254 stopped on idle CPUs are referred to as *tickless* systems and they are
256 which the tick cannot be stopped. If the given system is tickless, it will use
273 that the scheduler tick will be stopped. That time, referred to as the *sleep
333 the tick has not been stopped already (in a previous iteration of the idle
/Documentation/admin-guide/blockdev/drbd/
Ddrbd-connection-state-overview.dot83 CommTrouble -> Unconnected [label="receiver thread is stopped" ]
/Documentation/networking/device_drivers/atm/
Dcxacru.rst14 so it had no effect on the device configuration. Fixing it could have stopped
/Documentation/ABI/testing/
Dsysfs-class-led-flash27 is stopped after this period of time has passed from the start
Dsysfs-class-remoteproc10 stopped (using /sys/class/remoteproc/.../state) and write a new filename.

12345