Home
last modified time | relevance | path

Searched full:respect (Results 1 – 25 of 797) sorted by relevance

12345678910>>...32

/kernel/linux/linux-5.10/arch/arm/mach-pxa/include/mach/
Dbitfield.h31 * with respect to bit 0.
41 * Shft Shift value of the bit field with respect to bit 0.
63 * FShft Shift value of the bit field with respect to bit 0.
/kernel/linux/linux-5.10/arch/arm/mach-sa1100/include/mach/
Dbitfield.h30 * with respect to bit 0.
40 * Shft Shift value of the bit field with respect to bit 0.
62 * FShft Shift value of the bit field with respect to bit 0.
/kernel/linux/linux-4.19/arch/arm/mach-pxa/include/mach/
Dbitfield.h31 * with respect to bit 0.
41 * Shft Shift value of the bit field with respect to bit 0.
63 * FShft Shift value of the bit field with respect to bit 0.
/kernel/linux/linux-4.19/arch/arm/mach-sa1100/include/mach/
Dbitfield.h30 * with respect to bit 0.
40 * Shft Shift value of the bit field with respect to bit 0.
62 * FShft Shift value of the bit field with respect to bit 0.
/kernel/linux/linux-4.19/drivers/staging/most/dim2/
Derrors.h35 * Configuration does not respect hardware limitations
41 * Buffer size does not respect hardware limitations
/kernel/linux/linux-5.10/drivers/staging/most/dim2/
Derrors.h35 * Configuration does not respect hardware limitations
41 * Buffer size does not respect hardware limitations
/kernel/linux/linux-5.10/drivers/soc/qcom/
Dkryo-l2-accessors.c22 * accesses, and system registers with respect to device memory
42 * accesses, and system registers with respect to device memory
/kernel/linux/linux-4.19/Documentation/RCU/
DUP.txt79 Quick Quiz #2: What locking restriction must RCU callbacks respect?
86 infrastructure -must- respect grace periods, and -must- invoke callbacks
107 What locking restriction must RCU callbacks respect?
/kernel/linux/linux-4.19/drivers/staging/mt7621-mmc/
DMakefile18 # NEITHER DOES MEDIATEK PROVIDE ANY WARRANTY WHATSOEVER WITH RESPECT TO THE
26 # CUMULATIVE LIABILITY WITH RESPECT TO THE MEDIATEK SOFTWARE RELEASED HEREUNDER WILL BE,
Dboard.h18 * NEITHER DOES MEDIATEK PROVIDE ANY WARRANTY WHATSOEVER WITH RESPECT TO THE
26 * CUMULATIVE LIABILITY WITH RESPECT TO THE MEDIATEK SOFTWARE RELEASED HEREUNDER WILL BE,
/kernel/linux/linux-5.10/drivers/iio/adc/
Dad7292.c156 * If channel is being sampled with respect to AGND: in ad7292_vin_range_multiplier()
160 * If channel is being sampled with respect to AVDD: in ad7292_vin_range_multiplier()
184 /* Sampling with respect to AGND */ in ad7292_vin_range_multiplier()
192 /* Sampling with respect to AVDD */ in ad7292_vin_range_multiplier()
/kernel/linux/linux-5.10/Documentation/RCU/
DUP.rst84 What locking restriction must RCU callbacks respect?
93 infrastructure *must* respect grace periods, and *must* invoke callbacks
114 What locking restriction must RCU callbacks respect?
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/
Dnvidia,tegra114-spi.txt29 Tegra SPI master with respect to outgoing Tegra SPI master clock.
34 clock with respect to the data from the SPI slave device.
/kernel/linux/linux-4.19/arch/powerpc/include/asm/
Dbarrier.h13 * by this processor have been performed (with respect to all other
30 * doesn't order loads with respect to previous stores. Lwsync can be
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt42 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
/kernel/linux/linux-5.10/Documentation/admin-guide/media/
Davermedia.rst43 functionality of the remaining device nodes in respect of the
44 Avermedia DVBT. However, full functionality in respect of
/kernel/linux/linux-4.19/kernel/sched/
Dmembarrier.c75 * be in program order with respect to the caller in membarrier_global_expedited()
155 * be in program order with respect to the caller in membarrier_private_expedited()
269 * is guaranteed to be ordered with respect to sys_membarrier(). If we use
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dbattery.txt3 Please note that not all charger drivers respect all of the properties.
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dbarrier.h17 * by this processor have been performed (with respect to all other
32 * doesn't order loads with respect to previous stores. Lwsync can be
/kernel/linux/linux-4.19/Documentation/scheduler/
Dsched-deadline.txt339 to the number of CPUs), then the scheduler is unable to respect all the
348 tasks will not be starved and the system might be able to respect all the
366 If D_i = P_i for all tasks, then EDF is able to respect all the deadlines
370 a task as WCET_i/min{D_i,P_i}, and EDF is able to respect all the deadlines
375 necessary: there are task sets that are schedulable, but do not respect the
380 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence
388 respect all of their deadlines in a time interval of size t, and comparing
470 allows to respect the jobs' absolute deadlines for this task (this is what is
473 this task, as it is not possible to respect its temporal constraints.
624 worst-case delay respect to the "deadline" parameter. If "deadline" = "period"
/kernel/linux/linux-5.10/Documentation/scheduler/
Dsched-deadline.rst345 to the number of CPUs), then the scheduler is unable to respect all the
354 tasks will not be starved and the system might be able to respect all the
374 If D_i = P_i for all tasks, then EDF is able to respect all the deadlines
378 a task as WCET_i/min{D_i,P_i}, and EDF is able to respect all the deadlines
385 necessary: there are task sets that are schedulable, but do not respect the
390 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence
400 respect all of their deadlines in a time interval of size t, and comparing
484 allows to respect the jobs' absolute deadlines for this task (this is what is
487 this task, as it is not possible to respect its temporal constraints.
641 worst-case delay respect to the "deadline" parameter. If "deadline" = "period"
/kernel/linux/linux-4.19/Documentation/driver-api/
Ddevice-io.rst73 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
114 (not that it's simply ordered with respect to other writes), since a
/kernel/linux/linux-5.10/Documentation/ABI/obsolete/
Dsysfs-class-dax11 1. Guarantees fault granularity with respect to a given
/kernel/linux/linux-4.19/kernel/
Drseq.c186 * Load and clear event mask atomically with respect to in rseq_need_restart()
260 * respect to other threads scheduled on the same CPU, and with respect
/kernel/linux/linux-5.10/kernel/
Drseq.c186 * Load and clear event mask atomically with respect to in rseq_need_restart()
259 * respect to other threads scheduled on the same CPU, and with respect

12345678910>>...32