Home
last modified time | relevance | path

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

1234

/linux-6.14.4/arch/csky/
DKconfig265 bool "Tightly-Coupled/Sram Memory"
268 The implementation are not only used by TCM (Tightly-Coupled Memory)
/linux-6.14.4/Documentation/arch/arm/
Dtcm.rst2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
/linux-6.14.4/Documentation/devicetree/bindings/serial/
Darm,dcc.yaml14 via JTAG can be also used as one of serial line tightly coupled with every
/linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt3 The NVIC provides an interrupt controller that is tightly coupled to
/linux-6.14.4/Documentation/driver-api/hte/
Dtegra-hte.rst19 instance supports timestamping GPIOs in real time as it is tightly coupled with
/linux-6.14.4/Documentation/sound/soc/
Doverview.rst11 * Codec drivers were often tightly coupled to the underlying SoC
/linux-6.14.4/Documentation/infiniband/
Dtag_matching.rst66 tightly synchronized with respect to the tag-matching operation, this shadow
/linux-6.14.4/drivers/usb/dwc2/
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-6.14.4/arch/arm/include/asm/
Dcp15.h107 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
/linux-6.14.4/Documentation/devicetree/bindings/pinctrl/
Dingenic,pinctrl.yaml14 For the Ingenic SoCs, pin control is tightly bound with GPIO ports. All pins
/linux-6.14.4/drivers/soc/qcom/
Drpmh-internal.h40 * SLEEP / WAKE TCSs. Things are tightly packed in the
/linux-6.14.4/tools/testing/selftests/timers/
Dadjtick.c74 /* Try to get a more tightly bound pairing */ in get_monotonic_and_raw()
/linux-6.14.4/include/linux/
Dcache.h46 * this. You want __read_mostly data to be tightly packed, so that in the
/linux-6.14.4/drivers/media/platform/mediatek/vpu/
Dmtk_vpu.h179 * Mapping the VPU's DTCM (Data Tightly-Coupled Memory) /
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-6.14.4/drivers/hid/i2c-hid/
Di2c-hid-of-elan.c168 * this touchscreen is tightly integrated with the panel and assumes
/linux-6.14.4/kernel/locking/
Dlockdep_internals.h107 * Stack-trace: tightly packed array of stack backtrace
/linux-6.14.4/arch/s390/boot/
Dkaslr.c171 * physmem_alloc_or_die(). These allocations are tightly packed together
/linux-6.14.4/arch/arm64/boot/dts/ti/
Dk3-am62a-mcu.dtsi151 /* Tightly coupled to M4F */
Dk3-am62-mcu.dtsi150 /* Tightly coupled to M4F */
Dk3-am62p-j722s-common-mcu.dtsi152 /* Tightly coupled to M4F */
/linux-6.14.4/drivers/bus/
DKconfig114 cores. This bus is for per-CPU tightly coupled devices such as the
/linux-6.14.4/drivers/power/supply/
Dab8500_bmdata.c200 * Internal resistance and factory resistance are tightly coupled in ab8500_bm_of_probe()
/linux-6.14.4/Documentation/timers/
Dhrtimers.rst20 mess. The timers.c code is very "tightly coded" around jiffies and
/linux-6.14.4/Documentation/power/regulator/
Dconsumer.rst165 Bespoke or tightly coupled drivers may want to directly control regulator

1234