From: Rahul Sharma <r-sharma3@ti.com>
To: <peda@lysator.liu.se>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <r-sharma3@ti.com>, <vigneshr@ti.com>
Subject: [PATCH 1/2] dt-bindings: mux-controller: ti: add binding for event mux router
Date: Fri, 28 Aug 2026 15:36:14 +0530 [thread overview]
Message-ID: <20260828100615.1700223-2-r-sharma3@ti.com> (raw)
In-Reply-To: <20260828100615.1700223-1-r-sharma3@ti.com>
Add binding for the event mux router of TI's K3 based SoC AM62L.
The TI K3 mux routers which route the GPIO input events or Time-Sync
events b/w peripherals instead of routing to a CPU.
Refer Section 10.2 and 10.2.1 of https://www.ti.com/lit/pdf/sprujb4
Signed-off-by: Rahul Sharma <r-sharma3@ti.com>
---
.../mux/ti,am62l-event-mux-router.yaml | 79 +++++++++++++++++++
1 file changed, 79 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mux/ti,am62l-event-mux-router.yaml
diff --git a/Documentation/devicetree/bindings/mux/ti,am62l-event-mux-router.yaml b/Documentation/devicetree/bindings/mux/ti,am62l-event-mux-router.yaml
new file mode 100644
index 000000000000..a5ba7f78a156
--- /dev/null
+++ b/Documentation/devicetree/bindings/mux/ti,am62l-event-mux-router.yaml
@@ -0,0 +1,79 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mux/ti,am62l-event-mux-router.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: TI Event Multiplexer on K3 SoCs
+
+maintainers:
+ - Rahul Sharma <r-sharma3@ti.com>
+
+description:
+ The TI K3 mux routers routes the GPIO input events or Time
+ Sync events between peripherals instead of routing to a CPU.
+
+allOf:
+ - $ref: mux-controller.yaml#
+
+properties:
+ compatible:
+ const: ti,am62l-event-mux-router
+
+ reg:
+ description: Register base address and size.
+ maxItems: 1
+
+ '#mux-control-cells':
+ const: 1
+ description:
+ Number of cells in a mux control specifier. This should be 1.
+ The cell specifies which mux control to use (0-based index).
+
+ ti,reg-mask-val:
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+ items:
+ items:
+ - description: Register offset (relative to reg base)
+ - description: Bit mask for the mux control bits
+ - description: Value to write when mux is active (state 1)
+ minItems: 1
+ description: |
+ Array of triplets specifying register offset, mask, and value for each
+ mux control. Each triplet contains:
+ - register offset (relative to reg base)
+ - bit mask for the mux control bits
+ - value to write when mux is active (state 1)
+
+ idle-states:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ description: |
+ Idle state for each mux control. Each entry corresponds to a mux control:
+ - 0: clear masked bits when idle, also refers to inactive state
+ - 1: set configured value when idle, also refers to active state
+ - MUX_IDLE_AS_IS (-1): keep current state when idle
+
+required:
+ - compatible
+ - reg
+ - '#mux-control-cells'
+ - ti,reg-mask-val
+ - idle-states
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/mux/mux.h>
+
+ // Example 1: TI AM62L GPIO Mux Router
+ mux-controller@a00000 {
+ compatible = "ti,am62l-event-mux-router";
+ reg = <0xa00000 0x400>;
+ #mux-control-cells = <1>;
+
+ /* Mux Register addresses: 0xa00004 + (J × 4) */
+ /* GPIO0_40 -> BCDMA trigger 15 */
+ ti,reg-mask-val = <0x40 0x000ff 0x00028>;
+ idle-states = <0>;
+ };
--
2.34.1
next prev parent reply other threads:[~2026-08-28 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 10:06 [PATCH 0/2] Add TI's event mux router driver and build Rahul Sharma
2026-08-28 10:06 ` Rahul Sharma [this message]
2026-08-28 10:13 ` [PATCH 1/2] dt-bindings: mux-controller: ti: add binding for event mux router sashiko-bot
2026-08-28 11:50 ` Alvin Šipraga
2026-08-28 16:27 ` Conor Dooley
2026-08-28 10:06 ` [PATCH 2/2] mux-controller: ti: add driver " Rahul Sharma
2026-08-28 10:20 ` sashiko-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260828100615.1700223-2-r-sharma3@ti.com \
--to=r-sharma3@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@lysator.liu.se \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox