Skip to contentSkip to conversation

dt-bindings: i2c: intel,ixp4xx-i2c: Convert to DT schema

PATCH Superseded Shi Hao 2 participants 2 messages Mar 28 – Mar 29

Subsystems (2)

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore

Shi Hao

author
#0 lore raw

PATCH v2 1/1 dt-bindings: i2c: intel,ixp4xx-i2c: Convert to DT schema

Convert the IOP3xx and IXP4xx XScale bindings to DT schema. This conversion also adds the <irq.h> header file to the example section, since IRQ_TYPE_LEVEL_LOW macro is used. This ensures the examples validate correctly.

---

v2:

- Fix checkpatch.pl warnings
- Reorder compatibles in alphabetical order

Note:
* This patch is part of the GSoC2026 application process for device tree bindings conversions
* https://github.com/LinuxFoundationGSoC/ProjectIdeas/wiki/GSoC-2026-Device-Tree-Bindings

---
 .../devicetree/bindings/i2c/i2c-iop3xx.txt    | 20 ---------
 .../bindings/i2c/intel,ixp4xx-i2c.yaml        | 41 +++++++++++++++++++
 2 files changed, 41 insertions(+), 20 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-iop3xx.txt
 create mode 100644 Documentation/devicetree/bindings/i2c/intel,ixp4xx-i2c.yaml
Documentation/devicetree/bindings/i2c/i2c-iop3xx.txt deleted +0 -20
deleted file mode 100644
index dcc8390e0d24..000000000000
@@ -1,20 +0,0 @@
-i2c Controller on XScale platforms such as IOP3xx and IXP4xx
-
-Required properties:
-- compatible : Must be one of
-  "intel,iop3xx-i2c"
-  "intel,ixp4xx-i2c";
-- reg
-- #address-cells = <1>;
-- #size-cells = <0>;
-
-Optional properties:
-- Child nodes conforming to i2c bus binding
-
-Example:
-
-i2c@c8011000 {
-	compatible = "intel,ixp4xx-i2c";
-	reg = <0xc8011000 0x18>;
-	interrupts = <33 IRQ_TYPE_LEVEL_LOW>;
-};
Documentation/devicetree/bindings/i2c/intel,ixp4xx-i2c.yaml new file +41 -0

41 lines not on this page · raw message

Signature · 1 line
2.53.0
#1 lore raw
Quoted 4 lines · Shi Hao

Convert the IOP3xx and IXP4xx XScale bindings to DT schema. This conversion also adds the <irq.h> header file to the example section, since IRQ_TYPE_LEVEL_LOW macro is used. This ensures the examples validate correctly.

Drop last two sentences, irrelevant. I asked about changes in the binding, not in the example. The example is not relevant here and we never ask to document changes in it.
Did binding have interrupts? No.
Does new binding have interrupts? Yes.
Does your commit msg explains adding them? No.

Best regards,
Krzysztof