~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/devicetree/bindings/mailbox/mediatek,gce-props.yaml

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/devicetree/bindings/mailbox/mediatek,gce-props.yaml (Architecture i386) and /Documentation/devicetree/bindings/mailbox/mediatek,gce-props.yaml (Architecture alpha)


  1 # SPDX-License-Identifier: (GPL-2.0-only OR BS      1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
  2 %YAML 1.2                                           2 %YAML 1.2
  3 ---                                                 3 ---
  4 $id: http://devicetree.org/schemas/mailbox/med      4 $id: http://devicetree.org/schemas/mailbox/mediatek,gce-props.yaml#
  5 $schema: http://devicetree.org/meta-schemas/co      5 $schema: http://devicetree.org/meta-schemas/core.yaml#
  6                                                     6 
  7 title: MediaTek Global Command Engine Common P      7 title: MediaTek Global Command Engine Common Properties
  8                                                     8 
  9 maintainers:                                        9 maintainers:
 10   - Houlong Wei <houlong.wei@mediatek.com>          10   - Houlong Wei <houlong.wei@mediatek.com>
 11                                                    11 
 12 description:                                       12 description:
 13   The Global Command Engine (GCE) is an instru     13   The Global Command Engine (GCE) is an instruction based, multi-threaded,
 14   single-core command dispatcher for MediaTek      14   single-core command dispatcher for MediaTek hardware. The Command Queue
 15   (CMDQ) mailbox driver is a driver for GCE, i     15   (CMDQ) mailbox driver is a driver for GCE, implemented using the Linux
 16   mailbox framework. It is used to receive mes     16   mailbox framework. It is used to receive messages from mailbox consumers
 17   and configure GCE to execute the specified i     17   and configure GCE to execute the specified instruction set in the message.
 18   We use mediatek,gce-mailbox.yaml to define t     18   We use mediatek,gce-mailbox.yaml to define the properties for CMDQ mailbox
 19   driver. A device driver that uses the CMDQ d     19   driver. A device driver that uses the CMDQ driver to configure its hardware
 20   registers is a mailbox consumer. The mailbox     20   registers is a mailbox consumer. The mailbox consumer can request a mailbox
 21   channel corresponding to a GCE hardware thre     21   channel corresponding to a GCE hardware thread to send a message, specifying
 22   that the GCE thread to configure its hardwar     22   that the GCE thread to configure its hardware. The mailbox provider can also
 23   reserve a mailbox channel to configure GCE h     23   reserve a mailbox channel to configure GCE hardware register by the specific
 24   GCE thread. This binding defines the common      24   GCE thread. This binding defines the common GCE properties for both mailbox
 25   provider and consumers.                          25   provider and consumers.
 26                                                    26 
 27 properties:                                        27 properties:
 28   mediatek,gce-events:                             28   mediatek,gce-events:
 29     description:                                   29     description:
 30       GCE has an event table in SRAM, consisti     30       GCE has an event table in SRAM, consisting of 1024 event IDs (0~1023).
 31       Each event ID has a boolean event value      31       Each event ID has a boolean event value with the default value 0.
 32       The property mediatek,gce-events is used     32       The property mediatek,gce-events is used to obtain the event IDs.
 33       Some gce-events are hardware-bound and c     33       Some gce-events are hardware-bound and cannot be changed by software.
 34       For instance, in MT8195, when VDO0_MUTEX     34       For instance, in MT8195, when VDO0_MUTEX is stream done, VDO_MUTEX will
 35       send an event signal to GCE, setting the     35       send an event signal to GCE, setting the value of event ID 597 to 1.
 36       Similarly, in MT8188, the value of event     36       Similarly, in MT8188, the value of event ID 574 will be set to 1 when
 37       VOD0_MUTEX is stream done.                   37       VOD0_MUTEX is stream done.
 38       On the other hand, some gce-events are n     38       On the other hand, some gce-events are not hardware-bound and can be
 39       changed by software. For example, in MT8     39       changed by software. For example, in MT8188, we can set the value of
 40       event ID 855, which is not bound to any      40       event ID 855, which is not bound to any hardware, to 1 when the driver
 41       in the secure world completes a task. Ho     41       in the secure world completes a task. However, in MT8195, event ID 855
 42       is already bound to VDEC_LAT1, so we nee     42       is already bound to VDEC_LAT1, so we need to select another event ID to
 43       achieve the same purpose. This event ID      43       achieve the same purpose. This event ID can be any ID that is not bound
 44       to any hardware and is not yet used in a     44       to any hardware and is not yet used in any software driver.
 45       To determine if the event ID is bound to     45       To determine if the event ID is bound to the hardware or used by a
 46       software driver, refer to the GCE header     46       software driver, refer to the GCE header
 47       include/dt-bindings/gce/<chip>-gce.h of      47       include/dt-bindings/gce/<chip>-gce.h of each chip.
 48     $ref: /schemas/types.yaml#/definitions/uin     48     $ref: /schemas/types.yaml#/definitions/uint32-array
 49     minItems: 1                                    49     minItems: 1
 50     maxItems: 32                                   50     maxItems: 32
 51                                                    51 
 52 additionalProperties: true                         52 additionalProperties: true
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php