Searched full:happens (Results 1 – 25 of 271) sorted by relevance
1234567891011
/Documentation/i2c/busses/ |
D | i2c-ali1563.rst | 22 notable exceptions. One of those happens to be the fact they upgraded the 23 i2c core to be SMBus 2.0 compliant, and happens to be almost identical to
|
/Documentation/ABI/testing/ |
D | sysfs-devices-state_synced | 19 which happens only when all its consumer devices are registered 26 sync_state() call happens independent of the state of the
|
D | sysfs-devices-real_power_state | 19 the same device object. If that happens, some shared power
|
D | sysfs-bus-dfl-devices-n3000-nios | 9 happens when the Nios firmware version major < 3, or no link is
|
/Documentation/core-api/ |
D | debug-objects.rst | 78 problem before the real initialization of the object happens. E.g. it 101 problem before the real initialization of the object happens. E.g. it 125 problem before the real activation of the object happens. E.g. it can 165 before the real destruction of the object happens. E.g. it can 181 object happens. E.g. it can deactivate an active object in order to
|
D | boot-time-mm.rst | 37 really happens under the hood.
|
/Documentation/devicetree/bindings/watchdog/ |
D | da9062-wdt.txt | 13 - dlg,wdt-sd: Set what happens on watchdog timeout. If this bit is set the
|
/Documentation/trace/ |
D | osnoise-tracer.rst | 36 events. When a noise happens without any interference from the operating 104 higher than the configured value happens. Writing 0 disables this 107 higher than the configured value happens. Writing 0 disables this 171 The reason roots in the overhead of the entry and exit code that happens
|
/Documentation/devicetree/bindings/reset/ |
D | ti,sci-reset.yaml | 16 between the host processor running an OS and the system controller happens
|
/Documentation/devicetree/bindings/clock/ |
D | ti,sci-clk.yaml | 16 between the host processor running an OS and the system controller happens
|
/Documentation/timers/ |
D | highres.rst | 161 calls when an interrupt happens. The overhead would be much larger than the 174 When the timer interrupt happens, the next event interrupt handler is called 224 called when an interrupt happens during the idle period, which does not cause a 233 hrtimer_update_jiffies() is called from irq_enter() when an interrupt happens
|
/Documentation/bpf/ |
D | prog_cgroup_sysctl.rst | 72 written to sysctl before actual write happens. This helper can be used only 76 written to sysctl before actual write happens. Sysctl value will be
|
/Documentation/process/ |
D | volatile-considered-harmful.rst | 69 hyperthreaded twin processor; it also happens to serve as a compiler 79 ensures that the access happens as expected by the programmer.
|
D | maintainer-tip.rst | 50 - interrupt core development happens in the irq/core branch 52 - interrupt chip driver development also happens in the irq/core 59 happens in the timers/core branch, but patches are usually applied in 62 - clocksource/event driver development happens in the timers/core 68 - perf core and architecture support development happens in the 71 - perf tooling development happens in the perf tools maintainer 88 RCU development happens in the linux-rcu tree. The resulting changes
|
/Documentation/arch/parisc/ |
D | debugging.rst | 39 happens when the Q bit is cleared is the CPU does not update the
|
/Documentation/devicetree/bindings/soc/ti/ |
D | sci-pm-domain.yaml | 19 between the host processor running an OS and the system controller happens
|
/Documentation/arch/x86/ |
D | usb-legacy-support.rst | 25 The Intel E7505 is a typical machine where this happens.
|
/Documentation/kbuild/ |
D | Kconfig.recursion-issue-01 | 33 # tools run in a loop. When this happens Kconfig exits and complains about
|
/Documentation/mm/ |
D | hwpoison.rst | 25 when that happens another machine check will happen. 122 memory failure happens, this feature is disabled.
|
/Documentation/driver-api/media/ |
D | v4l2-device.rst | 40 be ``NULL``, but it happens with ISA devices or when one device creates 59 happens the parent device becomes invalid. Since :c:type:`v4l2_device` has a
|
/Documentation/input/devices/ |
D | edt-ft5x06.rst | 53 mode. The same happens when reading/writing to the parameter files when the
|
/Documentation/admin-guide/ |
D | edid.rst | 13 booting or it displays the wrong area. Cases when this happens are:
|
/Documentation/locking/ |
D | robust-futexes.rst | 92 registration happens at most once per thread lifetime]. At do_exit() 139 - no per-lock kernel allocation happens. 187 thread lifetime, and the cleanup operation, if it happens, is fast and
|
/Documentation/PCI/ |
D | pcieaer-howto.rst | 144 fatal error happens. The Root Port AER service driver provides a 209 What happens if a PCIe device driver does not provide an 218 What happens if an upstream port service driver does not provide
|
/Documentation/core-api/irq/ |
D | irqflags-tracing.rst | 10 happens in the kernel.
|
1234567891011