Remove undocumented IMR-LX4 device nodes
Get series with b4
b4 am 154807139502.25511.1919986589060151108.sendpatchset@octoVersions newest first
- v1 Latest2 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodesarch/ | +0 | 2 replies | |
| 2/2 | arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodesarch/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH/RFC 00/02] Remove undocumented IMR-LX4 device nodes
Remove undocumented IMR-LX4 device nodes
[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes
These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!
So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.
In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.
Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.
---
Developed on top of v5.0-rc3
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 40 ------------------------------ arch/arm64/boot/dts/renesas/r8a7796.dtsi | 20 --------------- 2 files changed, 60 deletions(-)