Home
last modified time | relevance | path

Searched full:respected (Results 1 – 25 of 77) sorted by relevance

1234

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/
Dimx7ulp-pcc-clock.yaml30 respected power domain.
/kernel/linux/linux-5.10/Documentation/staging/
Dspeculation.rst71 respected even under speculation. Architectures which are affected by
/kernel/linux/linux-6.6/Documentation/staging/
Dspeculation.rst71 respected even under speculation. Architectures which are affected by
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/
Dimx7ulp-pcc-clock.yaml30 respected power domain.
/kernel/linux/linux-6.6/drivers/hwtracing/coresight/
Dcoresight-syscfg.h89 * dependencies are respected.
/kernel/linux/linux-5.10/kernel/dma/
DKconfig217 Perform extra checking that callers of dma_map_sg() have respected the
/kernel/linux/linux-6.6/Documentation/process/
Dcontribution-maturity-model.rst17 respected leaders and eventually, kernel maintainers. To support a
/kernel/linux/linux-6.6/Documentation/scheduler/
Dsched-deadline.rst63 (clearly, if the system is overloaded this guarantee cannot be respected).
376 possible to formally check if all the deadlines are respected.
477 are respected, then SCHED_DEADLINE can be used to schedule real-time tasks
478 guaranteeing that all the jobs' deadlines of a task are respected.
561 As already stated in Section 3, a necessary condition to be respected to
/kernel/linux/linux-5.10/Documentation/scheduler/
Dsched-deadline.rst63 (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-6.6/drivers/net/ethernet/freescale/enetc/
Denetc_ierb.c72 * memory to ensure that the transmit allocation is respected. in enetc_ierb_register_pf()
/kernel/linux/linux-6.6/kernel/dma/
DKconfig253 Perform extra checking that callers of dma_map_sg() have respected the
/kernel/linux/linux-6.6/drivers/usb/serial/
Dkeyspan_usa90msg.h111 is respected
Dkeyspan_usa28msg.h132 port ends in a TX_OFF state); any non-zero value is respected
Dkeyspan_usa67msg.h171 port ends in a TX_OFF state); any non-zero value is respected
/kernel/linux/linux-5.10/drivers/usb/serial/
Dkeyspan_usa90msg.h111 is respected
Dkeyspan_usa28msg.h132 port ends in a TX_OFF state); any non-zero value is respected
Dkeyspan_usa67msg.h171 port ends in a TX_OFF state); any non-zero value is respected
/kernel/linux/linux-5.10/net/wireless/
Dreg.h127 * be respected but if a user had set the regulatory domain that will take
/kernel/linux/linux-6.6/net/wireless/
Dreg.h126 * be respected but if a user had set the regulatory domain that will take
/kernel/linux/linux-5.10/drivers/lightnvm/
Dpblk-rl.c239 /* Maximize I/O size and ansure that back threshold is respected */ in pblk_rl_init()
/kernel/linux/linux-5.10/Documentation/networking/
Dsegmentation-offloads.rst160 IP segments, padding respected. So unlike regular GSO, SCTP can't just
/kernel/linux/linux-6.6/Documentation/networking/
Dsegmentation-offloads.rst160 IP segments, padding respected. So unlike regular GSO, SCTP can't just
/kernel/linux/linux-6.6/tools/testing/selftests/mm/
Dmemfd_secret.c83 pass("mlock limit is respected\n"); in test_mlock_limit()
/kernel/linux/linux-6.6/drivers/net/wireless/ti/wl1251/
Dacx.h561 * during this Rx will always be respected and gain the antenna.
565 /* Max time the BT HP will be respected. */
568 /* Max time the WLAN HP will be respected. */
/kernel/linux/linux-5.10/drivers/net/wireless/ti/wl1251/
Dacx.h561 * during this Rx will always be respected and gain the antenna.
565 /* Max time the BT HP will be respected. */
568 /* Max time the WLAN HP will be respected. */

1234