Home
last modified time | relevance | path

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

12

/Linux-v6.1/Documentation/devicetree/bindings/clock/
Dimx7ulp-pcc-clock.yaml30 respected power domain.
/Linux-v6.1/Documentation/staging/
Dspeculation.rst71 respected even under speculation. Architectures which are affected by
/Linux-v6.1/drivers/hwtracing/coresight/
Dcoresight-syscfg.h89 * dependencies are respected.
/Linux-v6.1/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
/Linux-v6.1/kernel/dma/
DKconfig225 Perform extra checking that callers of dma_map_sg() have respected the
/Linux-v6.1/drivers/net/ethernet/freescale/enetc/
Denetc_ierb.c72 * memory to ensure that the transmit allocation is respected. in enetc_ierb_register_pf()
/Linux-v6.1/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
Dkeyspan_usa26msg.h175 port ends in a TX_OFF state); any non-zero value is respected
Dkeyspan_usa49msg.h176 port ends in a TX_OFF state); any non-zero value is respected
/Linux-v6.1/net/wireless/
Dreg.h126 * be respected but if a user had set the regulatory domain that will take
/Linux-v6.1/Documentation/networking/
Dsegmentation-offloads.rst160 IP segments, padding respected. So unlike regular GSO, SCTP can't just
Dregulatory.rst35 expected regulatory domains will be respected by the kernel.
/Linux-v6.1/tools/testing/selftests/vm/
Dmemfd_secret.c80 pass("mlock limit is respected\n"); in test_mlock_limit()
/Linux-v6.1/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. */
/Linux-v6.1/Documentation/trace/coresight/
Dcoresight-cpu-debug.rst106 respected in these cases, so these designs do not support debug over
/Linux-v6.1/arch/x86/math-emu/
Dfpu_emu.h137 that protection is respected in a segmented model. */
/Linux-v6.1/drivers/misc/habanalabs/common/
Dmemory.c634 /* Hint must be respected, so here we just fail */ in get_va_block()
636 "Hint address 0x%llx is not page aligned - cannot be respected\n", in get_va_block()
699 /* Hint address must be respected. If we are here - this means in get_va_block()
703 "Hint address 0x%llx could not be respected\n", in get_va_block()
1191 /* Fail if hint must be respected but it can't be */ in map_device_va()
1193 "Hint address 0x%llx cannot be respected because source memory is not aligned 0x%x\n", in map_device_va()
/Linux-v6.1/Documentation/arm64/
Dbooting.rst103 little-endian and must be respected. Where image_size is zero,
/Linux-v6.1/drivers/regulator/
Dbd71815-regulator.c241 * by SW the ramp-rate is not respected. Should we disable in buck12_set_hw_dvs_levels()
/Linux-v6.1/net/8021q/
Dvlan.c115 * grace period is respected before device freeing, in unregister_vlan_dev()
/Linux-v6.1/Documentation/block/
Dbfq-iosched.rst334 respected (see the description of how BFQ works, and, if needed, the
/Linux-v6.1/tools/firewire/
Dnosy-dump.c539 /* check that retry protocol is respected. */ in handle_request_packet()
/Linux-v6.1/drivers/media/i2c/
Dmt9v111.c749 /* Make sure frame rate/image sizes constraints are respected. */ in mt9v111_s_frame_interval()

12