Searched full:respect (Results 1 – 25 of 107) sorted by relevance
12345
| /Documentation/RCU/ |
| D | UP.rst | 85 What locking restriction must RCU callbacks respect?
102 infrastructure *must* respect grace periods, and *must* invoke callbacks
123 What locking restriction must RCU callbacks respect?
|
| /Documentation/admin-guide/media/ |
| D | avermedia.rst | 43 functionality of the remaining device nodes in respect of the
44 Avermedia DVBT. However, full functionality in respect of
|
| /Documentation/devicetree/bindings/net/ |
| D | ti,dp83822.yaml | 68 Sets the voltage ratio (with respect to the nominal value)
77 Sets the voltage ratio (with respect to the nominal value)
|
| /Documentation/kbuild/ |
| D | Kconfig.select-break | 15 # The option B and C are clearly contradicting with respect to A.
|
| /Documentation/ABI/testing/ |
| D | configfs-rdma_cm | 4 Description: Interface is used to configure RDMA-cable HCAs in respect to
|
| D | sysfs-devices-physical_location | 6 the device connection point with respect to the system's
|
| /Documentation/hwmon/ |
| D | g760a.rst | 35 speed differs more than 20% with respect to the programmed fan speed;
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-vivid.rst | 18 corresponding controls of the vivid driver with respect to the range and default values.
|
| D | ext-ctrls-jpeg.rst | 27 input image is sampled, in respect to maximum sample rate in each
|
| /Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 42 from the sensor is used to figure out how the device is oriented with respect
95 respect to the local earth geomagnetic reference frame where (y) is in the
151 relative orientation of any given sensor of this type with respect to the
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,imr.yaml | 16 texture mapping and drawing with respect to any shape that is split into
|
| /Documentation/driver-api/ |
| D | device-io.rst | 73 While the basic functions are defined to be synchronous with respect to
74 each other and ordered with respect to each other the busses the devices
311 respect to each other. On some architectures, this relies on barriers in
327 On many platforms, I/O accesses must be aligned with respect to the access
346 not guaranteed to be ordered with respect to normal ioremap() MMIO register
377 still ordered with respect to other writes and reads from the same device, but
378 due to the posted write semantics, this is not the case with respect to other
|
| D | io_ordering.rst | 13 memory barrier op, mb(), only with respect to I/O).
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | intel,ce4100-lapic.yaml | 44 modes. With respect to boot/init time, mainly two interrupt
|
| /Documentation/scheduler/ |
| D | sched-deadline.rst | 348 to the number of CPUs), then the scheduler is unable to respect all the
357 tasks will not be starved and the system might be able to respect all the
377 If D_i = P_i for all tasks, then EDF is able to respect all the deadlines
381 a task as WCET_i/min{D_i,P_i}, and EDF is able to respect all the deadlines
388 necessary: there are task sets that are schedulable, but do not respect the
393 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence
403 respect all of their deadlines in a time interval of size t, and comparing
487 allows to respect the jobs' absolute deadlines for this task (this is what is
490 this task, as it is not possible to respect its temporal constraints.
644 worst-case delay respect to the "deadline" parameter. If "deadline" = "period"
|
| /Documentation/devicetree/bindings/power/ |
| D | amlogic,meson-gx-pwrc.txt | 12 The bindings must respect the power domain bindings as described in the file
|
| /Documentation/devicetree/bindings/dma/ |
| D | nvidia,tegra210-adma.yaml | 37 ascending order with respect to the DMA channel index.
|
| D | nvidia,tegra186-gpc-dma.yaml | 40 ascending order with respect to the DMA channel index.
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ti,tmp513.yaml | 38 will continue to work. The shunt value also need to respect:
|
| /Documentation/networking/devlink/ |
| D | index.rst | 30 sure to respect following rules:
|
| /Documentation/rust/ |
| D | general-information.rst | 110 #. Any ``unsafe`` blocks respect the safety contract necessary to call the
111 operations inside the block. Similarly, any ``unsafe impl``\ s respect the
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 44 any critical section with respect to the reclaim is started - e.g.
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 37 must be a physical address, and respect the alignment requirements
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 66 tightly synchronized with respect to the tag-matching operation, this shadow
|
| /Documentation/devicetree/bindings/dma/stm32/ |
| D | st,stm32-dma.yaml | 74 interrupts in ascending order with respect to the
|
12345