Searched full:once (Results 1 – 25 of 576) sorted by relevance
12345678910>>...24
| /Documentation/watchdog/ |
| D | watchdog-parameters.rst | 33 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 …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | of-xilinx-wdt.txt | 13 - xlnx,wdt-enable-once : 0 - Watchdog can be restarted
14 1 - Watchdog can be enabled just once
24 xlnx,wdt-enable-once = <0x0>;
|
| /Documentation/admin-guide/ |
| D | clearing-warn-once.rst | 4 WARN_ONCE / WARN_ON_ONCE / printk_once only emit a message once.
8 clears the state and allows the warnings to print once again.
|
| /Documentation/hwmon/ |
| D | adc128d818.rst | 39 is read at least once. This means that the cause for the alarm may
42 once, to ensure that alarms are reported to user space.
44 The ADC128D818 only updates its values approximately once per second;
|
| D | adt7462.rst | 30 programmable. Once configured, the ADT7462 will adjust the PWM outputs in
39 the registers more often than once every other second. Further,
40 configuration data is only read once per minute.
|
| D | adt7470.rst | 30 programmable. Once configured, the ADT7470 will adjust the PWM outputs in
41 registers more often than once every 5 seconds. Further, configuration data is
42 only read once per minute.
|
| D | it87.rst | 34 Datasheet: Once publicly available at the ITE website, but no longer
42 Datasheet: Once publicly available at the ITE website, but no longer
50 Datasheet: Once publicly available at the ITE website, but no longer
58 Datasheet: Once publicly available at the ITE website, but no longer
212 this value can currently only be read once at initialization time, so
246 Temperatures are measured in degrees Celsius. An alarm is triggered once
280 is read at least once. This means that the cause for the alarm may already
284 once-only alarms.
|
| D | lm78.rst | 45 Temperatures are measured in degrees Celsius. An alarm is triggered once
73 is read at least once. This means that the cause for the alarm may
77 miss once-only alarms.
|
| D | via686a.rst | 48 Temperatures are measured in degrees Celsius. An alarm is triggered once
65 is read at least once. This means that the cause for the alarm may
69 miss once-only alarms.
|
| D | lm80.rst | 67 is read at least once. This means that the cause for the alarm may
71 miss once-only alarms.
|
| D | smsc47m1.rst | 77 is read at least once. This means that the cause for the alarm may
81 miss once-only alarms.
|
| /Documentation/leds/ |
| D | ledtrig-transient.rst | 12 features that require an on or off state to be held just once and then stay in
43 being able to actually change the LED state. Once driver is resumed, triggers
97 is used to start a timer that runs once. This value doesn't
120 allow user app to set the time once and activate it to run it once for the
156 echo 1 > activate - start timer = duration to run once
157 echo 1 > activate - start timer = duration to run once
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 67 # echo "method-once" > /sys/module/acpi/parameters/trace_state
133 # echo "method-once" > trace_state
157 acpi.trace_method_name=\_SB.LID0._LID acpi.trace_state=opcode-once
209 "method-once"
213 during method execution of "trace_method_name" will be logged only once.
221 "opcode-once"
226 once.
|
| D | video_extension.rst | 108 Once user space tool receives this event, it can modify the backlight
114 This works for machines covered by case ii) in Section 2. Once the driver
120 recommended to disable this behaviour once a GUI environment starts up and
|
| /Documentation/driver-api/usb/ |
| D | bulk-streams.rst | 9 queued at once.
20 Once a buffer has been queued to a stream ring, the device is notified (through
55 Drivers will only be allowed to call this API once for the same endpoint
|
| /Documentation/crypto/ |
| D | crypto_engine.rst | 39 * ``prepare_crypt_hardware``: Called once before any prepare functions are
42 * ``unprepare_crypt_hardware``: Called once after all unprepare functions have
|
| /Documentation/power/ |
| D | apm-acpi.rst | 19 once. Some people with broken ACPI or broken APM implementations
22 interface can be in control of the machine at once. Think about it..
|
| /Documentation/media/uapi/mediactl/ |
| D | request-api.rst | 88 Once the configuration and buffers of the request are specified, it can be
122 once all its associated buffers are available for dequeuing and all the
143 that file descriptor unusable and the request will be freed once it is no
188 Once the request is fully prepared, it can be queued to the driver:
228 Once we don't need the request anymore, we can either recycle it for reuse with
268 Once the request is fully prepared, it can be queued to the driver:
|
| /Documentation/hid/ |
| D | hid-transport.rst | 67 device. Once a device is registered with HID core, the callbacks provided via
72 device failures. Once transport drivers detect unplug or failure events, they
218 Once hid_add_device() is entered, HID core might use the callbacks provided in
226 Once hid_destroy_device() returns, HID core will no longer make use of any
238 Called from HID device drivers once they want to use the device. Transport
247 Called from HID device drivers once they are done with a device. Transport
259 Called from HID device drivers once they are interested in data reports.
262 However, once ->open() is called, transport drivers must be ready for I/O.
281 Called once during device setup after ->start() has been called. Transport
|
| D | uhid.rst | 23 device with the HID subsystem, then you need to open /dev/uhid once for each
69 the device on the control channel. Once the device responds, you must forward
178 Once you read a GET_REPORT request, you shall forward it to the hid device and
179 remember the "id" field in the payload. Once your hid device responds to the
187 send a SET_REPORT request to your hid device. Once it replies, you must tell
|
| /Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 16 We log things in order of completion once we are sure the write is no longer in
22 This works by attaching all WRITE requests to a list once the write completes.
23 Once we see a REQ_PREFLUSH request we splice this list onto the request and once
|
| /Documentation/netlabel/ |
| D | lsm_interface.rst | 46 sidestep much of this overhead once a mapping has been established. Once the
|
| /Documentation/scsi/ |
| D | scsi.txt | 26 once the scsi core is present in the kernel (either compiled in or loaded
31 and then unload it once you have no further need for the driver (and release
|
| /Documentation/driver-api/ |
| D | vme.rst | 51 Once a driver has registered with the VME core the provided match routine will
78 Functions are also provided to free window allocations once they are no longer
95 Once a master window has been assigned :c:func:`vme_master_set` can be used to
125 Once a slave window has been assigned :c:func:`vme_slave_set` can be used to
205 return once the list has been executed.
259 Once a bank of location monitors has been allocated, the function
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-tegra-fuse | 5 and Tegra124 SoC's from NVIDIA. The efuses contain write once
|
12345678910>>...24