Claude review: Revert "dt-bindings: display: bridge: ldb: Fill in reg property"

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

This reverts commit `16c8d76abe83`, removing the `reg` and `reg-names` property definitions themselves from the binding schema, and updating the example to match.

**Changes reviewed:**

Property definitions removed:
```yaml
-  reg:
-    maxItems: 2
-
-  reg-names:
-    items:
-      - const: ldb
-      - const: lvds
```

Example updated — removes `#address-cells`, `#size-cells` from the parent `blk-ctrl` node, and `reg`/`reg-names` from the bridge child:
```yaml
-        #address-cells = <1>;
-        #size-cells = <1>;
-
-        bridge@5c {
+        bridge {
             compatible = "fsl,imx8mp-ldb";
-            reg = <0x5c 0x4>, <0x128 0x4>;
-            reg-names = "ldb", "lvds";
```

**Assessment:** Correct. The resulting binding file (verified above) is clean and consistent. The example no longer needs `#address-cells`/`#size-cells` in the parent since no child has a `reg` property with a unit address. The binding still has `additionalProperties: false`, which will correctly reject any DTS that still tries to pass `reg` — this is fine since patches 3 and 4 clean up the actual DTS files.

**One observation:** Since `additionalProperties: false` is set, after this patch but before patches 3-4, running `dt_binding_check` against the existing imx8mp/imx6sx DTS files would produce schema validation warnings (the DTS files still have `reg` properties that the schema now disallows). This is a transient bisection issue — not a problem in practice since the series is applied atomically, but worth noting. Some maintainers prefer DTS changes before binding changes to avoid this. The current ordering (binding first, DTS second) is also commonly accepted.

**No blocking issues.**

---

---
Generated by Claude Code Patch Reviewer