Home
last modified time | relevance | path

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

123

/Linux-v6.1/arch/csky/
DKconfig269 bool "Tightly-Coupled/Sram Memory"
272 The implementation are not only used by TCM (Tightly-Coupled Meory)
/Linux-v6.1/Documentation/arm/
Dtcm.rst2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
/Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt3 The NVIC provides an interrupt controller that is tightly coupled to
/Linux-v6.1/fs/xfs/libxfs/
Dxfs_attr_sf.h12 * Small attribute lists are packed as tightly as possible so as
/Linux-v6.1/Documentation/driver-api/hte/
Dtegra194-hte.rst21 and AON GPIO controller are tightly coupled as it requires very specific bits
/Linux-v6.1/include/linux/
Dcache.h20 * this. You want __read_mostly data to be tightly packed, so that in the
/Linux-v6.1/Documentation/sound/soc/
Doverview.rst11 * Codec drivers were often tightly coupled to the underlying SoC
/Linux-v6.1/Documentation/infiniband/
Dtag_matching.rst66 tightly synchronized with respect to the tag-matching operation, this shadow
/Linux-v6.1/arch/arm/include/asm/
Dcp15.h107 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
/Linux-v6.1/drivers/soc/qcom/
Drpmh-internal.h40 * SLEEP / WAKE TCSs. Things are tightly packed in the
/Linux-v6.1/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-v6.1/Documentation/devicetree/bindings/pinctrl/
Dingenic,pinctrl.yaml14 For the Ingenic SoCs, pin control is tightly bound with GPIO ports. All pins
/Linux-v6.1/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-v6.1/tools/testing/selftests/timers/
Dadjtick.c78 /* Try to get a more tightly bound pairing */ in get_monotonic_and_raw()
/Linux-v6.1/kernel/locking/
Dlockdep_internals.h107 * Stack-trace: tightly packed array of stack backtrace
/Linux-v6.1/drivers/bus/
DKconfig114 cores. This bus is for per-CPU tightly coupled devices such as the
/Linux-v6.1/Documentation/devicetree/bindings/leds/
Dcommon.yaml21 have to be tightly coupled with the LED device binding. They are represented
/Linux-v6.1/drivers/power/supply/
Dab8500_bmdata.c200 * Internal resistance and factory resistance are tightly coupled in ab8500_bm_of_probe()
/Linux-v6.1/Documentation/scheduler/
Dsched-stats.rst20 cpus on the machine, while domain0 is the most tightly focused domain,
/Linux-v6.1/Documentation/driver-api/
Dpps.rst203 computers' clock to be synchronized very tightly. One way to do this is to
/Linux-v6.1/Documentation/power/regulator/
Dconsumer.rst165 Bespoke or tightly coupled drivers may want to directly control regulator
/Linux-v6.1/Documentation/timers/
Dhrtimers.rst20 mess. The timers.c code is very "tightly coded" around jiffies and
/Linux-v6.1/drivers/gpu/drm/i915/
Di915_vma_types.h219 * This is a tightly bound, fairly small number of users, so we
/Linux-v6.1/Documentation/networking/
Dsfp-phylink.rst218 tightly integrated, or when the settings are not coming from in-band

123