[PATCH 2/5] dt-bindings: connector: Add fsl,io-connector binding
Chancel Liu
chancel.liu at nxp.com
Fri May 8 19:48:43 PDT 2026
The NXP I/O connector represents a physically present I/O connector on
the base board. It acts as a nexus that exposes a constrained set of
I/O resources, such as GPIOs, clocks, PWMs and interrupts, through
fixed electrical wiring. All actual hardware providers reside on the
base board. The connector node only defines index-based mappings to
those providers.
Signed-off-by: Chancel Liu <chancel.liu at nxp.com>
---
.../bindings/connector/fsl,io-connector.yaml | 94 +++++++++++++++++++
1 file changed, 94 insertions(+)
create mode 100644 Documentation/devicetree/bindings/connector/fsl,io-connector.yaml
diff --git a/Documentation/devicetree/bindings/connector/fsl,io-connector.yaml b/Documentation/devicetree/bindings/connector/fsl,io-connector.yaml
new file mode 100644
index 000000000000..8b5038a2332e
--- /dev/null
+++ b/Documentation/devicetree/bindings/connector/fsl,io-connector.yaml
@@ -0,0 +1,94 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/connector/fsl,io-connector.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NXP I/O Connector
+
+maintainers:
+ - Frank Li <Frank.li at nxp.com>
+ - Chancel Liu <chancel.liu at nxp.com>
+
+description:
+ The NXP I/O connector represents a physically present I/O connector on the
+ base board. It acts as a nexus that exposes a constrained set of I/O
+ resources, such as GPIOs, clocks, PWMs and interrupts, through fixed
+ electrical wiring. All actual hardware providers reside on the base board.
+ The connector node only defines index-based mappings to those providers.
+
+properties:
+ compatible:
+ const: fsl,io-connector
+
+ gpio-controller: true
+
+ '#gpio-cells':
+ const: 2
+
+ gpio-map:
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+
+ gpio-map-mask:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ gpio-map-pass-thru:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ '#clock-cells':
+ const: 1
+
+ clock-map:
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+
+ clock-map-mask:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ clock-map-pass-thru:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ pwm-map:
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+
+ pwm-map-mask:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ pwm-map-pass-thru:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ '#address-cells':
+ const: 0
+
+ interrupt-controller: true
+
+ "#interrupt-cells":
+ const: 2
+
+ interrupt-map: true
+
+ interrupt-map-mask: true
+
+required:
+ - compatible
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ connector {
+ compatible = "fsl,io-connector";
+ gpio-controller;
+ #gpio-cells = <2>;
+ gpio-map = <0 0 &gpio1 8 1>;
+ gpio-map-mask = <0xff 0x0>;
+ gpio-map-pass-thru = <0x0 0x1>;
+ #clock-cells = <1>;
+ clock-map = <0 &clk 1>;
+ #address-cells = <0>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ interrupt-map-mask = <0xff 0x0>;
+ interrupt-map = <0 0 &gpio2 27 IRQ_TYPE_LEVEL_LOW>;
+ };
--
2.50.1
More information about the linux-arm-kernel
mailing list