summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorlhxj <[email protected]>2025-12-25 17:56:52 +0800
committerR b b666 <[email protected]>2026-01-20 22:05:28 +0800
commit7641ef68855601bc73252546bf41a96d6078444e (patch)
tree58e3dcf31552a868ab1bbd27b8c07ab731c2dede /src
parent306505ea24d22f908e052836918029d82259bc83 (diff)
[drivers] Fix OFW bus conflict and prevent duplicate device creation
Problem: When enumerating device tree nodes, platform bus and native buses (I2C/SPI) may create duplicate devices for the same OFW node, causing cross-bus conflicts. This triggers assertion failure '(dev->bus != new_bus)' in rt_bus_reload_driver_device() during boot on minimal DM-enabled systems. Root Cause: 1. Platform bus tries to reload devices that already belong to other buses by calling rt_bus_reload_driver_device(dev->bus, dev), which violates the API contract (requires dev->bus != new_bus). 2. Native buses (I2C/SPI) do not mark OFW nodes as occupied, so platform bus creates duplicate platform devices for I2C/SPI client nodes. Solution: 1. components/drivers/core/platform_ofw.c: Return RT_EOK when np->dev exists, letting the native bus handle device lifecycle instead of cross-bus reload. 2. components/drivers/i2c/dev_i2c_bus.c: Mark i2c_client_np->dev during scan to prevent platform bus from duplicating I2C client devices. 3. components/drivers/spi/dev_spi_bus.c: Mark spi_dev_np->dev during scan to prevent platform bus from duplicating SPI devices. Tested on Spacemit K1 RISC-V platform with minimal DM configuration. Signed-off-by: lhxj <[email protected]>
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions