Home
last modified time | relevance | path

Searched full:masters (Results 1 – 25 of 368) sorted by relevance

12345678910>>...15

/kernel/linux/linux-4.19/Documentation/trace/
Dstm.rst9 these masters and channels are statically allocated to certain
21 master 7 channel 15, while arbitrary user applications can use masters
26 identifiers to ranges of masters and channels. If these rules (policy)
31 have a name (string identifier) and a range of masters and channels
39 channels masters
40 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
46 masters 48 through 63 and channel allocation pool has channels 0
/kernel/linux/linux-5.10/Documentation/trace/
Dstm.rst11 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-5.10/drivers/vme/bridges/
Dvme_fake.c65 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-4.19/drivers/vme/bridges/
Dvme_fake.c69 struct fake_master_window masters[FAKE_MAX_MASTER]; member
321 bridge->masters[i].enabled = enabled; in fake_master_set()
322 bridge->masters[i].vme_base = vme_base; in fake_master_set()
323 bridge->masters[i].size = size; in fake_master_set()
324 bridge->masters[i].aspace = aspace; in fake_master_set()
325 bridge->masters[i].cycle = cycle; in fake_master_set()
326 bridge->masters[i].dwidth = dwidth; in fake_master_set()
353 *enabled = bridge->masters[i].enabled; in __fake_master_get()
354 *vme_base = bridge->masters[i].vme_base; in __fake_master_get()
355 *size = bridge->masters[i].size; in __fake_master_get()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/
Diommu.txt49 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-4.19/Documentation/devicetree/bindings/iommu/
Darm,smmu.txt5 of address translation to bus masters external to the CPU.
43 SMMUs with stream matching support and complex masters
55 masters connected upstream of the SMMU.
76 - mmu-masters (deprecated in favour of the generic "iommus" binding) :
78 masters for which the SMMU can provide a translation
Diommu.txt49 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
122 * Masters are statically associated with this IOMMU and share
124 * have sufficient information to distinguish between masters.
127 * all masters at any given point in time.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Ddma-router.yaml25 dma-masters:
37 - dma-masters
49 dma-masters = <&sdma>;
Dsnps,dw-axi-dmac.txt9 - snps,dma-masters: Number of AXI masters supported by the hardware.
34 snps,dma-masters = <2>;
Dst,stm32-dmamux.yaml34 - dma-masters
49 dma-masters = <&dma1 &dma2>;
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/dma/
Dsnps,dw-axi-dmac.txt9 - snps,dma-masters: Number of AXI masters supported by the hardware.
34 snps,dma-masters = <2>;
Dsnps-dma.txt9 - dma-masters: Number of AHB masters supported by the controller
41 dma-masters = <2>;
Ddma.txt41 - dma-masters: phandle of the DMA controller or list of phandles for
49 - In the node pointed by the dma-masters:
60 dma-masters = <&sdma>;
/kernel/linux/linux-5.10/drivers/fsi/
Dfsi-master.h4 * 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-4.19/Documentation/devicetree/bindings/fsi/
Dfsi.txt11 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-5.10/Documentation/devicetree/bindings/fsi/
Dfsi.txt11 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-5.10/Documentation/ABI/testing/
Dsysfs-class-stm1 What: /sys/class/stm/<stm>/masters
24 assigned masters.
Dconfigfs-stp-policy34 What: /config/stp-policy/<device>.<policy>/<node>/masters
38 Range of masters from which to allocate for users of this node.
/kernel/linux/linux-4.19/Documentation/ABI/testing/
Dsysfs-class-stm1 What: /sys/class/stm/<stm>/masters
24 assigned masters.
Dconfigfs-stp-policy34 What: /config/stp-policy/<device>.<policy>/<node>/masters
38 Range of masters from which to allocate for users of this node.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/bus/
Dbrcm,gisb-arb.txt19 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-4.19/Documentation/devicetree/bindings/bus/
Dbrcm,gisb-arb.txt18 masters are valid at the system level
20 masters. Should match the number of bits set in brcm,gisb-master-mask and
/kernel/linux/linux-4.19/drivers/dma/
Dstm32-dmamux.c54 u32 dma_reqs[]; /* Number of DMA Request per DMA masters.
55 * [0] holds number of DMA Masters.
140 dma_spec->np = of_parse_phandle(ofdma->of_node, "dma-masters", i - 1); in stm32_dmamux_route_allocate()
202 count = device_property_read_u32_array(&pdev->dev, "dma-masters", in stm32_dmamux_probe()
216 dma_node = of_parse_phandle(node, "dma-masters", i - 1); in stm32_dmamux_probe()
/kernel/linux/linux-5.10/drivers/i2c/muxes/
Di2c-mux-pca9541.c29 * The PCA9541 is a bus master selector. It supports two I2C masters connected
38 * This driver assumes that the two bus masters are controlled by two different
39 * hosts. If a single host controls both masters, platform code has to ensure
40 * that only one of the masters is instantiated at any given time.
158 * The main contention point occurs if the slave bus is off and both masters
/kernel/linux/linux-4.19/drivers/i2c/muxes/
Di2c-mux-pca9541.c29 * The PCA9541 is a bus master selector. It supports two I2C masters connected
38 * This driver assumes that the two bus masters are controlled by two different
39 * hosts. If a single host controls both masters, platform code has to ensure
40 * that only one of the masters is instantiated at any given time.
158 * The main contention point occurs if the slave bus is off and both masters

12345678910>>...15