Claude review: mfd: lm3533: Convert to use OF bindings

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

Patch Review

This is the largest patch and has several bugs:

**Critical — MFD cell ID mismatch**: The LED MFD cells are defined with `cell->id` = 0,1,2,3:
```c
MFD_CELL_OF_REG("lm3533-leds", NULL, NULL, 0, 0, "ti,lm3533-leds", 2),
MFD_CELL_OF_REG("lm3533-leds", NULL, NULL, 0, 1, "ti,lm3533-leds", 3),
MFD_CELL_OF_REG("lm3533-leds", NULL, NULL, 0, 2, "ti,lm3533-leds", 4),
MFD_CELL_OF_REG("lm3533-leds", NULL, NULL, 0, 3, "ti,lm3533-leds", 5),
```
Since `devm_mfd_add_devices` is called with `id=0`, `pdev->id = 0 + cell->id`, giving 0,1,2,3. But in `lm3533_led_probe`, the check is:
```c
if (pdev->id < LM3533_LVCTRLBANK_MIN || pdev->id > LM3533_LVCTRLBANK_MAX)
```
where `LM3533_LVCTRLBANK_MIN=2`. So LED cells with `pdev->id` 0 and 1 will **always fail probe with `-EINVAL`**. And `led->id = pdev->id - LM3533_LVCTRLBANK_MIN` will produce wrong/negative values for cells 0 and 1.

Fix: The cell IDs should be 2,3,4,5 to match the DT reg values.

**DT property name mismatch**: The binding defines `ti,resistor-ohm`, but the driver reads a different name:
```c
device_property_read_u32(&pdev->dev, "ti,resistor-value-ohm",
                         &als->r_select);
```
This will silently fail to read the property on all boards that use the documented binding name.

**Dead code**: The `have_als`, `have_backlights`, `have_leds` flags are computed by scanning child nodes but never read anywhere in the new code — they're dead stores. Since `devm_mfd_add_devices` always registers all 7 cells regardless of these flags, the iteration and flag-setting should either be removed or used to conditionally register cells.

**Removed `iio_device_set_parent`**: The line `iio_device_set_parent(indio_dev, pdev->dev.parent)` is deleted without comment. This changes the IIO device's parent from the i2c device to the platform device. If this is intentional (for proper OF node association), it should be mentioned in the commit message.

**Minor — `linux,default-trigger` property**: The LEDs driver reads `linux,default-trigger` via `device_property_read_string`, but the DT binding in Patch 1 doesn't document this property (though it inherits from `common.yaml` which may cover it).

---
Generated by Claude Code Patch Reviewer