| /openbmc/webui-vue/docs/guide/unit-testing/ |
| H A D | readme.md | 5 require consistent updating when refactoring code are likely tightly coupled to
69 - If test cases fail during refactoring, the test case may be tightly coupled
159 - Tightly coupled with implementation details
|
| /openbmc/linux/arch/csky/ |
| H A D | Kconfig | 266 bool "Tightly-Coupled/Sram Memory"
269 The implementation are not only used by TCM (Tightly-Coupled Memory)
|
| /openbmc/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).
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | arm,nvic.txt | 3 The NVIC provides an interrupt controller that is tightly coupled to
|
| /openbmc/linux/fs/xfs/libxfs/ |
| H A D | xfs_attr_sf.h | 12 * Small attribute lists are packed as tightly as possible so as
|
| /openbmc/phosphor-post-code-manager/ |
| H A D | README.md | 27 This repository is tightly coupled with
|
| /openbmc/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
|
| /openbmc/linux/include/linux/ |
| H A D | cache.h | 20 * this. You want __read_mostly data to be tightly packed, so that in the
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | overview.rst | 11 * Codec drivers were often tightly coupled to the underlying SoC
|
| /openbmc/openbmc-test-automation/redfish/extended/ |
| H A D | test_basic_ci.robot | 32 # Application services running on the BMC are not tightly coupled.
|
| /openbmc/linux/Documentation/infiniband/ |
| H A D | tag_matching.rst | 66 tightly synchronized with respect to the tag-matching operation, this shadow
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | xlnx,zynqmp-r5fss.yaml | 45 tightly coupled memories (TCM). System memory is cacheable, but the TCM
|
| /openbmc/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
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | ingenic,pinctrl.yaml | 14 For the Ingenic SoCs, pin control is tightly bound with GPIO ports. All pins
|
| /openbmc/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.
|
| /openbmc/linux/drivers/soc/qcom/ |
| H A D | rpmh-internal.h | 40 * SLEEP / WAKE TCSs. Things are tightly packed in the
|
| /openbmc/linux/drivers/hid/i2c-hid/ |
| H A D | i2c-hid-of-elan.c | 161 * this touchscreen is tightly integrated with the panel and assumes
|
| /openbmc/linux/tools/testing/selftests/timers/ |
| H A D | adjtick.c | 78 /* Try to get a more tightly bound pairing */ in get_monotonic_and_raw()
|
| /openbmc/linux/drivers/media/platform/mediatek/vpu/ |
| H A D | mtk_vpu.h | 179 * Mapping the VPU's DTCM (Data Tightly-Coupled Memory) /
|
| H A D | mtk_vpu.c | 33 /* 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
|
| /openbmc/linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-am62a-mcu.dtsi | 143 /* Tightly coupled to M4F */
|
| H A D | k3-am62-mcu.dtsi | 147 /* Tightly coupled to M4F */
|
| /openbmc/linux/kernel/locking/ |
| H A D | lockdep_internals.h | 107 * Stack-trace: tightly packed array of stack backtrace
|
| /openbmc/linux/arch/s390/boot/ |
| H A D | kaslr.c | 171 * physmem_alloc_top_down(). These allocations are tightly packed together
|
| /openbmc/linux/drivers/bus/ |
| H A D | Kconfig | 114 cores. This bus is for per-CPU tightly coupled devices such as the
|