| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | mtk-gce.txt | 1 MediaTek GCE
4 The Global Command Engine (GCE) is used to help read/write registers with
6 vblank. The GCE can be used to implement the Command Queue (CMDQ) driver.
12 - compatible: can be "mediatek,mt8173-gce", "mediatek,mt8183-gce",
13 "mediatek,mt8186-gce", "mediatek,mt8192-gce", "mediatek,mt8195-gce" or
14 "mediatek,mt6779-gce".
15 - reg: Address range of the GCE unit
16 - interrupts: The interrupt signal from the GCE block
18 - clock-names: Must be "gce" to stand for GCE clock
21 phandle: Label name of a gce node.
[all …]
|
| H A D | mediatek,gce-mailbox.yaml | 4 $id: http://devicetree.org/schemas/mailbox/mediatek,gce-mailbox.yaml#
13 The Global Command Engine (GCE) is used to help read/write registers with
15 vblank. The GCE can be used to implement the Command Queue (CMDQ) driver.
21 - mediatek,mt6779-gce
22 - mediatek,mt8173-gce
23 - mediatek,mt8183-gce
24 - mediatek,mt8186-gce
25 - mediatek,mt8188-gce
26 - mediatek,mt8192-gce
27 - mediatek,mt8195-gce
[all …]
|
| H A D | mediatek,gce-props.yaml | 4 $id: http://devicetree.org/schemas/mailbox/mediatek,gce-props.yaml#
13 The Global Command Engine (GCE) is an instruction based, multi-threaded,
15 (CMDQ) mailbox driver is a driver for GCE, implemented using the Linux
17 and configure GCE to execute the specified instruction set in the message.
18 We use mediatek,gce-mailbox.yaml to define the properties for CMDQ mailbox
21 channel corresponding to a GCE hardware thread to send a message, specifying
22 that the GCE thread to configure its hardware. The mailbox provider can also
23 reserve a mailbox channel to configure GCE hardware register by the specific
24 GCE thread. This binding defines the common GCE properties for both mailbox
28 mediatek,gce-events:
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/media/ |
| H A D | mediatek,mdp3-rsz.yaml | 29 mediatek,gce-client-reg:
33 - description: phandle of GCE
34 - description: GCE subsys id
37 description: The register of client driver can be configured by gce with
38 4 arguments defined in this property. Each GCE subsys id is mapping to
39 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
41 mediatek,gce-events:
44 to gce. The event id is defined in the gce heade
[all...] |
| H A D | mediatek,mdp3-wrot.yaml | 29 mediatek,gce-client-reg:
33 - description: phandle of GCE
34 - description: GCE subsys id
37 description: The register of client driver can be configured by gce with
38 4 arguments defined in this property. Each GCE subsys id is mapping to
39 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
41 mediatek,gce-events:
44 to gce. The event id is defined in the gce heade
[all...] |
| H A D | mediatek,mdp3-rdma.yaml | 36 mediatek,gce-client-reg:
40 - description: phandle of GCE
41 - description: GCE subsys id
44 description: The register of client driver can be configured by gce with
45 4 arguments defined in this property. Each GCE subsys id is mapping to
46 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
48 mediatek,gce-events:
51 to gce. The event id is defined in the gce header
52 include/dt-bindings/gce/<chip>-gce.h of each chips.
93 - mediatek,gce-client-reg
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/mediatek/ |
| H A D | mediatek,ccorr.yaml | 25 mediatek,gce-client-reg:
29 - description: phandle of GCE
30 - description: GCE subsys id
33 description: The register of client driver can be configured by gce with
34 4 arguments defined in this property. Each GCE subsys id is mapping to
35 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
37 mediatek,gce-events:
40 to gce. The event id is defined in the gce header
41 include/dt-bindings/gce/<chip>-gce.h of each chips.
50 - mediatek,gce-client-reg
[all …]
|
| H A D | mediatek,wdma.yaml | 26 mediatek,gce-client-reg:
30 - description: phandle of GCE
31 - description: GCE subsys id
34 description: The register of client driver can be configured by gce with
35 4 arguments defined in this property. Each GCE subsys id is mapping to
36 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
38 mediatek,gce-events:
41 to gce. The event id is defined in the gce header
42 include/dt-bindings/gce/<chip>-gce.h of each chips.
57 - mediatek,gce-client-reg
[all …]
|
| H A D | mediatek,mutex.yaml | 57 mediatek,gce-events:
60 to gce. The event id is defined in the gce header
61 include/dt-bindings/gce/<chip>-gce.h of each chips.
64 mediatek,gce-client-reg:
68 - description: phandle of GCE
69 - description: GCE subsys id
72 description: The register of client driver can be configured by gce with
73 4 arguments defined in this property. Each GCE subsys id is mapping to
74 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
108 #include <dt-bindings/gce/mt8173-gce.h>
[all …]
|
| /freebsd/release/ |
| H A D | Makefile.gce | 7 GCE_UPLOAD_TGTS= gce-check-depends \
8 gce-do-package \
9 gce-do-upload
13 GCE_UPLOAD_TGTS= gce-do-login
29 gce-upload: ${GCE_UPLOAD_TGTS}
31 gce-check-depends:
33 . if !defined(GCE${VAR}) || empty(GCE${VAR})
34 @echo "Variable GCE${VAR} cannot be empty."
55 gce
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/arm/mediatek/ |
| H A D | mediatek,mmsys.yaml | 73 Using mailbox to communicate with GCE, it should have this
75 Documentation/devicetree/bindings/mailbox/mediatek,gce-mailbox.yaml
79 mediatek,gce-client-reg:
81 The register of client driver can be configured by gce with 4 arguments
82 defined in this property, such as phandle of gce, subsys id,
85 register which is defined in the gce header
86 include/dt-bindings/gce/<chip>-gce.h.
106 #include <dt-bindings/gce/mt8173-gce
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/display/mediatek/ |
| H A D | mediatek,mdp-rdma.yaml | 42 mediatek,gce-client-reg:
44 The register of display function block to be set by gce. There are 4 arguments,
45 such as gce node, subsys id, offset and register size. The subsys id that is
46 mapping to the register of display function blocks is defined in the gce header
47 include/dt-bindings/gce/<chip>-gce.h of each chips.
51 - description: phandle of GCE
52 - description: GCE subsys id
63 - mediatek,gce-client-reg
72 #include <dt-bindings/gce/mt8195-gce.h>
86 mediatek,gce-client-reg = <&gce0 SUBSYS_1c10XXXX 0x4000 0x1000>;
|
| H A D | mediatek,postmask.yaml | 47 mediatek,gce-client-reg:
48 description: The register of client driver can be configured by gce with
49 4 arguments defined in this property, such as phandle of gce, subsys id,
50 register offset and size. Each GCE subsys id is mapping to a client
51 defined in the header include/dt-bindings/gce/<chip>-gce.h.
69 #include <dt-bindings/gce/mt8192-gce.h>
81 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xd000 0x1000>;
|
| H A D | mediatek,wdma.yaml | 50 mediatek,gce-client-reg:
51 description: The register of client driver can be configured by gce with
52 4 arguments defined in this property, such as phandle of gce, subsys id,
53 register offset and size. Each GCE subsys id is mapping to a client
54 defined in the header include/dt-bindings/gce/<chip>-gce.h.
73 #include <dt-bindings/gce/mt8173-gce.h>
87 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x1000 0x1000>;
|
| H A D | mediatek,ccorr.yaml | 52 mediatek,gce-client-reg:
53 description: The register of client driver can be configured by gce with
54 4 arguments defined in this property, such as phandle of gce, subsys id,
55 register offset and size. Each GCE subsys id is mapping to a client
56 defined in the header include/dt-bindings/gce/<chip>-gce.h.
74 #include <dt-bindings/gce/mt8183-gce.h>
86 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xf000 0x1000>;
|
| H A D | mediatek,dither.yaml | 51 mediatek,gce-client-reg:
52 description: The register of client driver can be configured by gce with
53 4 arguments defined in this property, such as phandle of gce, subsys id,
54 register offset and size. Each GCE subsys id is mapping to a client
55 defined in the header include/dt-bindings/gce/<chip>-gce.h.
73 #include <dt-bindings/gce/mt8183-gce.h>
85 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x2000 0x1000>;
|
| H A D | mediatek,ovl-2l.yaml | 52 mediatek,gce-client-reg:
53 description: The register of client driver can be configured by gce with
54 4 arguments defined in this property, such as phandle of gce, subsys id,
55 register offset and size. Each GCE subsys id is mapping to a client
56 defined in the header include/dt-bindings/gce/<chip>-gce.h.
75 #include <dt-bindings/gce/mt8183-gce.h>
89 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x9000 0x1000>;
|
| H A D | mediatek,aal.yaml | 57 mediatek,gce-client-reg:
58 description: The register of client driver can be configured by gce with
59 4 arguments defined in this property, such as phandle of gce, subsys id,
60 register offset and size. Each GCE subsys id is mapping to a client
61 defined in the header include/dt-bindings/gce/<chip>-gce.h.
79 #include <dt-bindings/gce/mt8173-gce.h>
91 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x5000 0x1000>;
|
| H A D | mediatek,gamma.yaml | 60 mediatek,gce-client-reg:
61 description: The register of client driver can be configured by gce with
62 4 arguments defined in this property, such as phandle of gce, subsys id,
63 register offset and size. Each GCE subsys id is mapping to a client
64 defined in the header include/dt-bindings/gce/<chip>-gce.h.
82 #include <dt-bindings/gce/mt8173-gce.h>
94 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x6000 0x1000>;
|
| H A D | mediatek,color.yaml | 60 mediatek,gce-client-reg:
61 description: The register of client driver can be configured by gce with
62 4 arguments defined in this property, such as phandle of gce, subsys id,
63 register offset and size. Each GCE subsys id is mapping to a client
64 defined in the header include/dt-bindings/gce/<chip>-gce.h.
82 #include <dt-bindings/gce/mt8173-gce.h>
94 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x3000 0x1000>;
|
| H A D | mediatek,ovl.yaml | 70 mediatek,gce-client-reg:
71 description: The register of client driver can be configured by gce with
72 4 arguments defined in this property, such as phandle of gce, subsys id,
73 register offset and size. Each GCE subsys id is mapping to a client
74 defined in the header include/dt-bindings/gce/<chip>-gce.h.
93 #include <dt-bindings/gce/mt8173-gce.h>
107 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xc000 0x1000>;
|
| H A D | mediatek,dsc.yaml | 41 mediatek,gce-client-reg:
43 The register of client driver can be configured by gce with 4 arguments
44 defined in this property, such as phandle of gce, subsys id,
47 register which is defined in the gce header
48 include/dt-bindings/gce/<chip>-gce.h.
66 #include <dt-bindings/gce/mt8195-gce.h>
78 mediatek,gce-client-reg = <&gce1 SUBSYS_1c00XXXX 0x9000 0x1000>;
|
| H A D | mediatek,split.yaml | 43 mediatek,gce-client-reg:
45 The register of display function block to be set by gce. There are 4 arguments,
46 such as gce node, subsys id, offset and register size. The subsys id that is
47 mapping to the register of display function blocks is defined in the gce header
48 include/dt-bindings/gce/<chip>-gce.h of each chips.
52 - description: phandle of GCE
53 - description: GCE subsys id
84 - mediatek,gce-client-reg
|
| H A D | mediatek,rdma.yaml | 82 mediatek,gce-client-reg:
83 description: The register of client driver can be configured by gce with
84 4 arguments defined in this property, such as phandle of gce, subsys id,
85 register offset and size. Each GCE subsys id is mapping to a client
86 defined in the header include/dt-bindings/gce/<chip>-gce.h.
105 #include <dt-bindings/gce/mt8173-gce.h>
120 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xe000 0x1000>;
|
| H A D | mediatek,mutex.yaml | 51 mediatek,gce-events:
54 to gce. The event id is defined in the gce header
55 include/dt-bindings/gce/<chip>-gce.h of each chips.
72 #include <dt-bindings/gce/mt8173-gce.h>
84 mediatek,gce-events = <CMDQ_EVENT_MUTEX0_STREAM_EOF>,
|