Home
last modified time | relevance | path

Searched full:behaves (Results 1 – 25 of 158) sorted by relevance

1234567

/linux/include/drm/
H A Ddrm_module.h51 * macro behaves like module_pci_driver() but tests the state of
87 * behaves like drm_module_pci_driver() with an additional driver-specific
114 * macro behaves like module_platform_driver() but tests the state of
/linux/arch/arm/boot/dts/nxp/imx/
H A Dimx6q-cm-fx6.dts181 * the module behaves unstable at this frequency. Hence, remove the
203 * the module behaves unstable at this frequency. Hence, remove the
225 * the module behaves unstable at this frequency. Hence, remove the
247 * the module behaves unstable at this frequency. Hence, remove the
/linux/kernel/trace/rv/monitors/sched/
H A DKconfig8 Collection of monitors to check the scheduler behaves according to specifications.
/linux/net/bridge/
H A Dbr_mrp.c208 /* In case the node behaves as MRA then the Test frame needs to have in br_mrp_alloc_test_skb()
274 * - when MRA behaves as MRM, in this case is similar with MRM role
275 * - when MRA behaves as MRC, in this case test_monitor is set to true,
297 * role MRA and behaves as MRC. The reason is that the in br_mrp_test_work_expired()
1112 * behaves as MRM node in br_mrp_rcv()
1140 /* Nodes that behaves as MRM needs to stop forwarding the in br_mrp_rcv()
1152 /* A node that behaves as MRC and doesn't have a interconnect in br_mrp_rcv()
/linux/Documentation/driver-api/usb/
H A Dpersist.rst26 By default, Linux behaves according to the spec. If a USB host
97 behaves as though the old device had been unplugged and a new device
/linux/Documentation/devicetree/bindings/clock/ti/
H A Dapll.txt8 modes (locked, low power stop etc.) APLL mostly behaves like
/linux/Documentation/devicetree/bindings/gpio/
H A Dfairchild,74hc595.yaml12 which behaves like an active-low chip select.
/linux/Documentation/hwmon/
H A Dnsa320.rst31 interface behaves similarly to SPI but at much lower speeds than are normally
H A Dasb100.rst64 I.e. it behaves the same as w83781d.
/linux/Documentation/driver-api/
H A Dsm501.rst66 The PCI driver assumes that the PCI card behaves as per the Silicon
/linux/Documentation/arch/s390/
H A D3270.rst115 you have chosen 3270 console support, your console now behaves
258 The IBM 3215 driver behaves similarly.
/linux/Documentation/sound/hd-audio/
H A Ddp-mst.rst10 several device entries. Each device entry behaves as a pin.
/linux/Documentation/devicetree/bindings/clock/
H A Dmediatek,mt8196-sys-clock.yaml70 As such, the HWV behaves more like a hardware-managed clock reference
H A Dmediatek,mt8196-clock.yaml75 As such, the HWV behaves more like a hardware-managed clock reference
/linux/drivers/scsi/
H A Dst_options.h94 /* If ST_SYSV is non-zero, the tape behaves according to the SYS V semantics.
/linux/Documentation/arch/x86/x86_64/
H A Dfred.rst71 LKGS behaves like the MOV to GS instruction except that it loads the
/linux/include/uapi/misc/
H A Dfastrpc.h37 * otherwise behaves similar to FASTRPC_MAP_FD_DELAYED flag.
/linux/tools/testing/selftests/powerpc/mm/
H A Dwild_bctr.c5 * Test that an out-of-bounds branch to counter behaves as expected.
/linux/arch/x86/mm/
H A Dtestmmiotrace.c96 * Tests how mmiotrace behaves in face of multiple ioremap / iounmaps in
/linux/arch/arm64/include/asm/
H A Dcache.h64 * Whilst the D-side always behaves as PIPT on AArch64, aliasing is
/linux/Documentation/sound/cards/
H A Dpcmtest.rst84 action can help you to figure out how the userspace ALSA program behaves under unusual
/linux/Documentation/admin-guide/device-mapper/
H A Dera.rst8 dm-era is a target that behaves similar to the linear target. In
/linux/kernel/time/
H A DKconfig142 By default, without passing the nohz_full parameter, this behaves just
/linux/arch/x86/math-emu/
H A Dreg_mul.c85 80486 behaves this way. in FPU_mul()
/linux/tools/power/cpupower/bench/
H A DREADME-BENCH97 governor in average behaves as expected.

1234567