Home
last modified time | relevance | path

Searched full:gce (Results 1 – 25 of 55) sorted by relevance

123

/freebsd/sys/contrib/device-tree/Bindings/mailbox/
H A Dmtk-gce.txt1 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 Dmediatek,gce-mailbox.yaml4 $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 Dmediatek,gce-props.yaml4 $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 Dmediatek,mdp3-rsz.yaml30 mediatek,gce-client-reg:
34 - description: phandle of GCE
35 - description: GCE subsys id
38 description: The register of client driver can be configured by gce with
39 4 arguments defined in this property. Each GCE subsys id is mapping to
40 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
42 mediatek,gce-events:
45 to gce. The event id is defined in the gce header
46 include/dt-bindings/gce/<chip>-gce.h of each chips.
55 - mediatek,gce-client-reg
[all …]
H A Dmediatek,mdp3-wrot.yaml30 mediatek,gce-client-reg:
34 - description: phandle of GCE
35 - description: GCE subsys id
38 description: The register of client driver can be configured by gce with
39 4 arguments defined in this property. Each GCE subsys id is mapping to
40 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
42 mediatek,gce-events:
45 to gce. The event id is defined in the gce header
46 include/dt-bindings/gce/<chip>-gce.h of each chips.
64 - mediatek,gce-client-reg
[all …]
H A Dmediatek,mdp3-rdma.yaml36 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 …]
H A Dmediatek,mdp3-fg.yaml29 mediatek,gce-client-reg:
31 The register of display function block to be set by gce. There are 4 arguments,
32 such as gce node, subsys id, offset and register size. The subsys id that is
33 mapping to the register of display function blocks is defined in the gce header
34 include/dt-bindings/gce/<chip>-gce.h of each chips.
38 - description: phandle of GCE
39 - description: GCE subsys id
50 - mediatek,gce-client-reg
58 #include <dt-bindings/gce/mt8195-gce.h>
63 mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x2000 0x1000>;
H A Dmediatek,mdp3-tdshp.yaml29 mediatek,gce-client-reg:
31 The register of display function block to be set by gce. There are 4 arguments,
32 such as gce node, subsys id, offset and register size. The subsys id that is
33 mapping to the register of display function blocks is defined in the gce header
34 include/dt-bindings/gce/<chip>-gce.h of each chips.
38 - description: phandle of GCE
39 - description: GCE subsys id
50 - mediatek,gce-client-reg
58 #include <dt-bindings/gce/mt8195-gce.h>
63 mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x7000 0x1000>;
H A Dmediatek,mdp3-stitch.yaml29 mediatek,gce-client-reg:
31 The register of display function block to be set by gce. There are 4 arguments,
32 such as gce node, subsys id, offset and register size. The subsys id that is
33 mapping to the register of display function blocks is defined in the gce header
34 include/dt-bindings/gce/<chip>-gce.h of each chips.
38 - description: phandle of GCE
39 - description: GCE subsys id
50 - mediatek,gce-client-reg
58 #include <dt-bindings/gce/mt8195-gce.h>
63 mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x3000 0x1000>;
H A Dmediatek,mdp3-tcc.yaml30 mediatek,gce-client-reg:
32 The register of display function block to be set by gce. There are 4 arguments,
33 such as gce node, subsys id, offset and register size. The subsys id that is
34 mapping to the register of display function blocks is defined in the gce header
35 include/dt-bindings/gce/<chip>-gce.h of each chips.
39 - description: phandle of GCE
40 - description: GCE subsys id
51 - mediatek,gce-client-reg
59 #include <dt-bindings/gce/mt8195-gce.h>
64 mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0xb000 0x1000>;
H A Dmediatek,mdp3-hdr.yaml29 mediatek,gce-client-reg:
31 The register of display function block to be set by gce. There are 4 arguments,
32 such as gce node, subsys id, offset and register size. The subsys id that is
33 mapping to the register of display function blocks is defined in the gce header
34 include/dt-bindings/gce/<chip>-gce.h of each chips.
38 - description: phandle of GCE
39 - description: GCE subsys id
50 - mediatek,gce-client-reg
58 #include <dt-bindings/gce/mt8195-gce.h>
63 mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x4000 0x1000>;
/freebsd/sys/contrib/device-tree/Bindings/soc/mediatek/
H A Dmediatek,ccorr.yaml25 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 Dmediatek,wdma.yaml26 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 Dmediatek,mutex.yaml57 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 DMakefile.gce5 GCE_UPLOAD_TGTS= gce-check-depends \
6 gce-do-package \
7 gce-do-upload
11 GCE_UPLOAD_TGTS= gce-do-login
35 gce-upload: ${GCE_UPLOAD_TGTS}
37 gce-check-depends:
39 . if !defined(GCE${VAR}) || empty(GCE${VAR})
40 @echo "Variable GCE${VAR} cannot be empty."
61 gce-do-login:
66 GCE_IMG_${_FS}= ${.OBJDIR}/gce.${_FS}.raw
[all …]
/freebsd/sys/contrib/device-tree/Bindings/arm/mediatek/
H A Dmediatek,mmsys.yaml73 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.
134 #include <dt-bindings/gce/mt8173-gce.h>
142 mboxes = <&gce 0 CMDQ_THR_PRIO_HIGHEST>,
143 <&gce 1 CMDQ_THR_PRIO_HIGHEST>;
[all …]
/freebsd/sys/contrib/device-tree/Bindings/display/mediatek/
H A Dmediatek,mdp-rdma.yaml42 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 Dmediatek,padding.yaml41 mediatek,gce-client-reg:
43 GCE (Global Command Engine) is a multi-core micro processor that helps
45 describes GCE client's information that is composed by 4 fields.
46 1. Phandle of the GCE (there may be several GCE processors)
48 (Please refer to include/dt-bindings/gce/<chip>-gce.h)
54 - description: Phandle of the GCE
65 - mediatek,gce-client-reg
74 #include <dt-bindings/gce/mt8195-gce.h>
85 mediatek,gce-client-reg = <&gce0 SUBSYS_1c11XXXX 0xd000 0x1000>;
H A Dmediatek,wdma.yaml50 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 Dmediatek,postmask.yaml47 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.
90 #include <dt-bindings/gce/mt8192-gce.h>
102 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xd000 0x1000>;
H A Dmediatek,ccorr.yaml52 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.
95 #include <dt-bindings/gce/mt8183-gce.h>
107 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xf000 0x1000>;
H A Dmediatek,dither.yaml51 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.
95 #include <dt-bindings/gce/mt8183-gce.h>
107 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x2000 0x1000>;
H A Dmediatek,ovl-2l.yaml52 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.
97 #include <dt-bindings/gce/mt8183-gce.h>
111 mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x9000 0x1000>;
H A Dmediatek,gamma.yaml60 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.
101 #include <dt-bindings/gce/mt8173-gce.h>
113 mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x6000 0x1000>;
H A Dmediatek,split.yaml43 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

123