Searched full:respected (Results 1 – 25 of 65) sorted by relevance
123
| /kernel/linux/linux-4.19/drivers/net/caif/ |
| D | caif_spi_slave.c | 152 * first loop. Make sure that minimum toggle time is respected. in cfspi_xfer()
178 /* Make sure that the minimum toggle time is respected. */ in cfspi_xfer()
|
| /kernel/linux/linux-4.19/arch/alpha/include/asm/ |
| D | barrier.h | 23 * These ordering constraints are respected by both the local CPU
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | speculation.txt | 69 respected even under speculation. Architectures which are affected by
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| D | speculation.rst | 71 respected even under speculation. Architectures which are affected by
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | imx7ulp-pcc-clock.yaml | 30 respected power domain.
|
| /kernel/linux/linux-5.10/kernel/dma/ |
| D | Kconfig | 217 Perform extra checking that callers of dma_map_sg() have respected the
|
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | sched-deadline.txt | 63 (clearly, if the system is overloaded this guarantee cannot be respected).
365 possible to formally check if all the deadlines are respected.
460 are respected, then SCHED_DEADLINE can be used to schedule real-time tasks
461 guaranteeing that all the jobs' deadlines of a task are respected.
543 As already stated in Section 3, a necessary condition to be respected to
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-deadline.rst | 63 (clearly, if the system is overloaded this guarantee cannot be respected).
373 possible to formally check if all the deadlines are respected.
474 are respected, then SCHED_DEADLINE can be used to schedule real-time tasks
475 guaranteeing that all the jobs' deadlines of a task are respected.
558 As already stated in Section 3, a necessary condition to be respected to
|
| /kernel/linux/linux-4.19/drivers/usb/serial/ |
| D | keyspan_usa90msg.h | 110 is respected
|
| D | keyspan_usa28msg.h | 131 port ends in a TX_OFF state); any non-zero value is respected
|
| D | keyspan_usa67msg.h | 170 port ends in a TX_OFF state); any non-zero value is respected
|
| D | keyspan_usa26msg.h | 174 port ends in a TX_OFF state); any non-zero value is respected
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| D | keyspan_usa90msg.h | 111 is respected
|
| D | keyspan_usa28msg.h | 132 port ends in a TX_OFF state); any non-zero value is respected
|
| D | keyspan_usa67msg.h | 171 port ends in a TX_OFF state); any non-zero value is respected
|
| D | keyspan_usa26msg.h | 175 port ends in a TX_OFF state); any non-zero value is respected
|
| /kernel/linux/linux-5.10/net/wireless/ |
| D | reg.h | 127 * be respected but if a user had set the regulatory domain that will take
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | segmentation-offloads.txt | 146 IP segments, padding respected. So unlike regular GSO, SCTP can't just
|
| D | regulatory.txt | 32 expected regulatory domains will be respected by the kernel.
|
| /kernel/linux/linux-4.19/net/wireless/ |
| D | reg.h | 125 * be respected but if a user had set the regulatory domain that will take
|
| /kernel/linux/linux-5.10/drivers/lightnvm/ |
| D | pblk-rl.c | 239 /* Maximize I/O size and ansure that back threshold is respected */ in pblk_rl_init()
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | segmentation-offloads.rst | 160 IP segments, padding respected. So unlike regular GSO, SCTP can't just
|
| D | regulatory.rst | 35 expected regulatory domains will be respected by the kernel.
|
| /kernel/linux/linux-4.19/Documentation/trace/ |
| D | coresight-cpu-debug.txt | 104 respected in these cases, so these designs do not support debug over
|
| /kernel/linux/linux-5.10/Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 106 respected in these cases, so these designs do not support debug over
|
123