/linux/Documentation/arch/arm/ |
H A D | tcm.rst | 2 ARM TCM (Tightly-Coupled Memory) handling in Linux 7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
|
/linux/Documentation/devicetree/bindings/serial/ |
H A D | arm,dcc.yaml | 14 via JTAG can be also used as one of serial line tightly coupled with every
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | arm,nvic.yaml | 13 The NVIC provides an interrupt controller that is tightly coupled to Cortex-M
|
/linux/Documentation/driver-api/hte/ |
H A D | tegra-hte.rst | 19 instance supports timestamping GPIOs in real time as it is tightly coupled with
|
/linux/Documentation/sound/soc/ |
H A D | overview.rst | 11 * Codec drivers were often tightly coupled to the underlying SoC
|
/linux/Documentation/infiniband/ |
H A D | tag_matching.rst | 66 tightly synchronized with respect to the tag-matching operation, this shadow
|
/linux/drivers/usb/dwc2/ |
H A D | hcd.h | 216 * the main bus schedule is tightly packed and this 217 * time should be interpreted as tightly packed (so 279 * is tightly packed.
|
/linux/arch/arm/include/asm/ |
H A D | cp15.h | 107 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
|
/linux/drivers/soc/qcom/ |
H A D | rpmh-internal.h | 40 * SLEEP / WAKE TCSs. Things are tightly packed in the
|
/linux/drivers/media/platform/mediatek/vpu/ |
H A D | mtk_vpu.h | 179 * Mapping the VPU's DTCM (Data Tightly-Coupled Memory) /
|
/linux/drivers/hid/i2c-hid/ |
H A D | i2c-hid-of-elan.c | 168 * this touchscreen is tightly integrated with the panel and assumes
|
/linux/kernel/locking/ |
H A D | lockdep_internals.h | 107 * Stack-trace: tightly packed array of stack backtrace
|
/linux/arch/s390/boot/ |
H A D | kaslr.c | 171 * physmem_alloc_or_die(). These allocations are tightly packed together
|
/linux/drivers/bus/ |
H A D | Kconfig | 114 cores. This bus is for per-CPU tightly coupled devices such as the
|
/linux/arch/arm64/boot/dts/ti/ |
H A D | k3-am62-mcu.dtsi | 150 /* Tightly coupled to M4F */
|
H A D | k3-am62a-mcu.dtsi | 150 /* Tightly coupled to M4F */
|
H A D | k3-am62p-j722s-common-mcu.dtsi | 152 /* Tightly coupled to M4F */
|
/linux/drivers/power/supply/ |
H A D | ab8500_bmdata.c | 200 * Internal resistance and factory resistance are tightly coupled in ab8500_bm_of_probe()
|
/linux/Documentation/timers/ |
H A D | hrtimers.rst | 20 mess. The timers.c code is very "tightly coded" around jiffies and
|
/linux/Documentation/power/regulator/ |
H A D | consumer.rst | 165 Bespoke or tightly coupled drivers may want to directly control regulator
|
/linux/Documentation/scheduler/ |
H A D | sched-stats.rst | 33 cpus on the machine, while domain0 is the most tightly focused domain,
|
/linux/tools/testing/selftests/bpf/progs/ |
H A D | core_reloc_types.h | 776 uint64_t ub2: 60; /* packed tightly */ 786 uint64_t ub2: 61; /* packed tightly */
|
/linux/drivers/firmware/efi/libstub/ |
H A D | fdt.c | 219 * exit_boot_services() call, so the exiting of boot services is very tightly
|
/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | xlnx,zynqmp-r5fss.yaml | 69 tightly coupled memories (TCM). System memory is cacheable, but the TCM
|
/linux/Documentation/devicetree/bindings/leds/ |
H A D | common.yaml | 21 have to be tightly coupled with the LED device binding. They are represented
|