Searched full:tightly (Results 1 – 25 of 67) sorted by relevance
123
| /linux-5.10/arch/csky/ |
| D | Kconfig | 226 bool "Tightly-Coupled/Sram Memory"
229 The implementation are not only used by TCM (Tightly-Coupled Meory)
|
| /linux-5.10/Documentation/arm/ |
| 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-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,nvic.txt | 3 The NVIC provides an interrupt controller that is tightly coupled to
|
| /linux-5.10/fs/xfs/libxfs/ |
| D | xfs_attr_sf.h | 12 * Small attribute lists are packed as tightly as possible so as
|
| D | xfs_attr.h | 20 * Small attribute lists use a different format and are packed as tightly
|
| /linux-5.10/include/linux/ |
| D | cache.h | 20 * this. You want __read_mostly data to be tightly packed, so that in the
|
| /linux-5.10/Documentation/sound/soc/ |
| D | overview.rst | 11 * Codec drivers were often tightly coupled to the underlying SoC
|
| /linux-5.10/Documentation/infiniband/ |
| D | tag_matching.rst | 66 tightly synchronized with respect to the tag-matching operation, this shadow
|
| /linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | ingenic,pinctrl.yaml | 14 For the Ingenic SoCs, pin control is tightly bound with GPIO ports. All pins
|
| /linux-5.10/arch/arm/include/asm/ |
| D | cp15.h | 107 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
|
| /linux-5.10/drivers/soc/qcom/ |
| D | rpmh-internal.h | 40 * SLEEP / WAKE TCSs. Things are tightly packed in the
|
| /linux-5.10/drivers/usb/dwc2/ |
| D | hcd.h | 245 * the main bus schedule is tightly packed and this
246 * time should be interpreted as tightly packed (so
308 * is tightly packed.
|
| /linux-5.10/tools/testing/selftests/timers/ |
| D | adjtick.c | 78 /* Try to get a more tightly bound pairing */ in get_monotonic_and_raw()
|
| /linux-5.10/drivers/media/platform/mtk-vpu/ |
| D | mtk_vpu.h | 177 * Mapping the VPU's DTCM (Data Tightly-Coupled Memory) /
|
| D | mtk_vpu.c | 32 /* maximum program/data TCM (Tightly-Coupled Memory) size */
93 * @tcm: the register for VPU Tightly-Coupled Memory
160 * struct share_obj - DTCM (Data Tightly-Coupled Memory) buffer shared with
|
| /linux-5.10/kernel/locking/ |
| D | lockdep_internals.h | 107 * Stack-trace: tightly packed array of stack backtrace
|
| /linux-5.10/drivers/bus/ |
| D | Kconfig | 103 cores. This bus is for per-CPU tightly coupled devices such as the
|
| /linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 21 have to be tightly coupled with the LED device binding. They are represented
|
| /linux-5.10/Documentation/scheduler/ |
| D | sched-stats.rst | 20 cpus on the machine, while domain0 is the most tightly focused domain,
|
| /linux-5.10/block/ |
| D | blk-mq.h | 261 * device, even if these context are synchronized to tightly control BIO issuing
|
| /linux-5.10/Documentation/timers/ |
| D | hrtimers.rst | 20 mess. The timers.c code is very "tightly coded" around jiffies and
|
| /linux-5.10/drivers/gpu/drm/i915/ |
| D | i915_vma_types.h | 205 * This is a tightly bound, fairly small number of users, so we
|
| /linux-5.10/Documentation/power/regulator/ |
| D | consumer.rst | 165 Bespoke or tightly coupled drivers may want to directly control regulator
|
| /linux-5.10/Documentation/driver-api/ |
| D | pps.rst | 203 computers' clock to be synchronized very tightly. One way to do this is to
|
| /linux-5.10/tools/testing/selftests/bpf/progs/ |
| D | core_reloc_types.h | 764 uint64_t ub2: 60; /* packed tightly */
774 uint64_t ub2: 61; /* packed tightly */
|
123