Home
last modified time | relevance | path

Searched full:tightly (Results 1 – 25 of 71) sorted by relevance

123

/linux/arch/csky/
H A DKconfig264 bool "Tightly-Coupled/Sram Memory"
267 The implementation are not only used by TCM (Tightly-Coupled Memory)
/linux/Documentation/arch/arm/
H A Dtcm.rst2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Darm,nvic.yaml13 The NVIC provides an interrupt controller that is tightly coupled to Cortex-M
/linux/Documentation/driver-api/hte/
H A Dtegra-hte.rst19 instance supports timestamping GPIOs in real time as it is tightly coupled with
/linux/Documentation/sound/soc/
H A Doverview.rst11 * Codec drivers were often tightly coupled to the underlying SoC
/linux/Documentation/userspace-api/fwctl/
H A Dfwctl.rst16 tightly coupled FW/HW combination is an effective risk mitigation against chip
87 3. Multiple VM functions tightly scoped within the VM
/linux/Documentation/infiniband/
H A Dtag_matching.rst66 tightly synchronized with respect to the tag-matching operation, this shadow
/linux/arch/arm/include/asm/
H A Dcp15.h107 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
/linux/drivers/usb/dwc2/
H A Dhcd.h216 * the main bus schedule is tightly packed and this
217 * time should be interpreted as tightly packed (so
279 * is tightly packed.
/linux/drivers/soc/qcom/
H A Drpmh-internal.h40 * SLEEP / WAKE TCSs. Things are tightly packed in the
/linux/include/linux/
H A Dcache.h43 * this. You want __read_mostly data to be tightly packed, so that in the
/linux/tools/testing/selftests/timers/
H A Dadjtick.c74 /* Try to get a more tightly bound pairing */ in get_monotonic_and_raw()
/linux/drivers/hid/i2c-hid/
H A Di2c-hid-of-elan.c168 * this touchscreen is tightly integrated with the panel and assumes
/linux/drivers/media/platform/mediatek/vpu/
H A Dmtk_vpu.h179 * Mapping the VPU's DTCM (Data Tightly-Coupled Memory) /
H A Dmtk_vpu.c33 /* maximum program/data TCM (Tightly-Coupled Memory) size */
100 * @tcm: the register for VPU Tightly-Coupled Memory
167 * struct share_obj - DTCM (Data Tightly-Coupled Memory) buffer shared with
/linux/kernel/locking/
H A Dlockdep_internals.h109 * Stack-trace: tightly packed array of stack backtrace
/linux/arch/s390/boot/
H A Dkaslr.c171 * physmem_alloc_or_die(). These allocations are tightly packed together
/linux/drivers/bus/
H A DKconfig120 cores. This bus is for per-CPU tightly coupled devices such as the
/linux/arch/arm64/boot/dts/ti/
H A Dk3-am62-mcu.dtsi150 /* Tightly coupled to M4F */
H A Dk3-am62a-mcu.dtsi150 /* Tightly coupled to M4F */
H A Dk3-am62p-j722s-common-mcu.dtsi152 /* Tightly coupled to M4F */
/linux/drivers/power/supply/
H A Dab8500_bmdata.c200 * Internal resistance and factory resistance are tightly coupled in ab8500_bm_of_probe()
/linux/Documentation/timers/
H A Dhrtimers.rst20 mess. The timers.c code is very "tightly coded" around jiffies and
/linux/drivers/gpu/drm/i915/
H A Di915_vma_types.h170 * This is a tightly bound, fairly small number of users, so we
/linux/Documentation/scheduler/
H A Dsched-stats.rst33 cpus on the machine, while domain0 is the most tightly focused domain,

123