| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 49 association of masters to be configured. Note that an IOMMU can by design
56 - #iommu-cells = <4>: Some IOMMU devices allow the DMA window for masters to
70 Devices that access memory through an IOMMU are called masters. A device can
91 - pasid-num-bits: Some masters support multiple address spaces for DMA, by
105 Firmware has to opt-in stalling, because most buses and masters don't
108 won't work in systems and masters that haven't been designed for
146 * Masters are statically associated with this IOMMU and share
148 * have sufficient information to distinguish between masters.
151 * all masters at any given point in time.
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | stm.rst | 11 these masters and channels are statically allocated to certain
23 master 7 channel 15, while arbitrary user applications can use masters
28 identifiers to ranges of masters and channels. If these rules (policy)
33 have a name (string identifier) and a range of masters and channels
41 channels masters
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
48 masters 48 through 63 and channel allocation pool has channels 0
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | stm.rst | 11 these masters and channels are statically allocated to certain
23 master 7 channel 15, while arbitrary user applications can use masters
28 identifiers to ranges of masters and channels. If these rules (policy)
33 have a name (string identifier) and a range of masters and channels
41 channels masters
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
48 masters 48 through 63 and channel allocation pool has channels 0
|
| /kernel/linux/linux-6.6/drivers/staging/vme_user/ |
| D | vme_fake.c | 65 struct fake_master_window masters[FAKE_MAX_MASTER]; member
317 bridge->masters[i].enabled = enabled; in fake_master_set()
318 bridge->masters[i].vme_base = vme_base; in fake_master_set()
319 bridge->masters[i].size = size; in fake_master_set()
320 bridge->masters[i].aspace = aspace; in fake_master_set()
321 bridge->masters[i].cycle = cycle; in fake_master_set()
322 bridge->masters[i].dwidth = dwidth; in fake_master_set()
348 *enabled = bridge->masters[i].enabled; in __fake_master_get()
349 *vme_base = bridge->masters[i].vme_base; in __fake_master_get()
350 *size = bridge->masters[i].size; in __fake_master_get()
[all …]
|
| /kernel/linux/linux-5.10/drivers/vme/bridges/ |
| D | vme_fake.c | 65 struct fake_master_window masters[FAKE_MAX_MASTER]; member
317 bridge->masters[i].enabled = enabled; in fake_master_set()
318 bridge->masters[i].vme_base = vme_base; in fake_master_set()
319 bridge->masters[i].size = size; in fake_master_set()
320 bridge->masters[i].aspace = aspace; in fake_master_set()
321 bridge->masters[i].cycle = cycle; in fake_master_set()
322 bridge->masters[i].dwidth = dwidth; in fake_master_set()
349 *enabled = bridge->masters[i].enabled; in __fake_master_get()
350 *vme_base = bridge->masters[i].vme_base; in __fake_master_get()
351 *size = bridge->masters[i].size; in __fake_master_get()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 49 association of masters to be configured. Note that an IOMMU can by design
56 - #iommu-cells = <4>: Some IOMMU devices allow the DMA window for masters to
70 Devices that access memory through an IOMMU are called masters. A device can
91 - pasid-num-bits: Some masters support multiple address spaces for DMA, by
128 * Masters are statically associated with this IOMMU and share
130 * have sufficient information to distinguish between masters.
133 * all masters at any given point in time.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | dma-router.yaml | 25 dma-masters:
37 - dma-masters
49 dma-masters = <&sdma>;
|
| D | snps,dw-axi-dmac.txt | 9 - snps,dma-masters: Number of AXI masters supported by the hardware.
34 snps,dma-masters = <2>;
|
| D | st,stm32-dmamux.yaml | 34 - dma-masters
49 dma-masters = <&dma1 &dma2>;
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/dma/ |
| D | dma-router.yaml | 25 dma-masters:
39 - dma-masters
51 dma-masters = <&sdma>;
|
| D | snps,dw-axi-dmac.yaml | 65 snps,dma-masters:
67 Number of AXI masters supported by the hardware.
109 - snps,dma-masters
149 snps,dma-masters = <2>;
|
| D | renesas,rzn1-dmamux.yaml | 30 dma-masters:
49 dma-masters = <&dma0 &dma1>;
|
| D | st,stm32-dmamux.yaml | 34 - dma-masters
49 dma-masters = <&dma1>, <&dma2>;
|
| /kernel/linux/linux-5.10/drivers/fsi/ |
| D | fsi-master.h | 4 * to allow the core to interact with the (hardware-specific) masters.
18 * These are used by hardware masters, such as the one in the FSP2, AST2600 and
59 #define FSI_MRESP_RST_ALL_MASTER 0x20000000 /* Reset all FSI masters */
77 * These are used by low level masters that bit-bang out the protocol
118 * These are common to all masters
|
| /kernel/linux/linux-6.6/drivers/fsi/ |
| D | fsi-master.h | 4 * to allow the core to interact with the (hardware-specific) masters.
18 * These are used by hardware masters, such as the one in the FSP2, AST2600 and
59 #define FSI_MRESP_RST_ALL_MASTER 0x20000000 /* Reset all FSI masters */
77 * These are used by low level masters that bit-bang out the protocol
118 * These are common to all masters
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/freescale/imx8mm/sys/ |
| D | metrics.json | 3 "BriefDescription": "bytes all masters read from ddr based on read-cycles event",
11 "BriefDescription": "bytes all masters write to ddr based on write-cycles event",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/freescale/imx8mn/sys/ |
| D | metrics.json | 3 "BriefDescription": "bytes all masters read from ddr based on read-cycles event",
11 "BriefDescription": "bytes all masters write to ddr based on write-cycles event",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/freescale/imx8mq/sys/ |
| D | metrics.json | 3 "BriefDescription": "bytes all masters read from ddr based on read-cycles event",
11 "BriefDescription": "bytes all masters write to ddr based on write-cycles event",
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 11 FSI masters may require their own DT nodes (to describe the master HW itself);
15 Under the masters' nodes, we can describe the bus topology using nodes to
43 FSI masters
62 masters that may be present on the bus.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 11 FSI masters may require their own DT nodes (to describe the master HW itself);
15 Under the masters' nodes, we can describe the bus topology using nodes to
43 FSI masters
62 masters that may be present on the bus.
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-stm | 1 What: /sys/class/stm/<stm>/masters
24 assigned masters.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-stm | 1 What: /sys/class/stm/<stm>/masters
24 assigned masters.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/ |
| D | cci-control-port.yaml | 7 title: CCI Interconnect Bus Masters
13 Masters in the device tree connected to a CCI port (inclusive of CPUs
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/bus/ |
| D | brcm,gisb-arb.txt | 19 masters are valid at the system level
21 masters. Should match the number of bits set in brcm,gisb-master-mask and
|
| /kernel/linux/linux-6.6/drivers/soundwire/ |
| D | intel_bus_common.c | 80 * case if one or more masters remain active. In this condition, in intel_start_bus_after_reset()
81 * all the masters are powered on for they are in the same power in intel_start_bus_after_reset()
265 * all the Masters in the steam with the expectation that in intel_post_bank_switch()
267 * and do nothing for the other Masters in intel_post_bank_switch()
|