dmitriy/rk3588_flake
1
0
Fork 0
Code Issues 5 Pull requests Projects Releases 1 Packages Wiki Activity Actions

Fix the regulators #1

New issue
Open
opened 2025-08-24 16:26:06 -06:00 by dmitriy · 1 comment
dmitriy commented 2025-08-24 16:26:06 -06:00
Owner
Copy link

There's something wrong with the rockchip-pm-domain device tree config. I'm getting the following errors in dmesg:

[   11.023991] rockchip-pm-domain fd8d8000.power-management:power-controller: failed to set domain 'nputop' on, val=0


[   11.081941] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier 2-0042 for /power-management@fd8d8000/power-controller/power-domain@8

[   37.865766] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdba4000.video-codec
[   37.865778] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdba8000.video-codec
[   37.865782] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdbac000.video-codec

In our NPU DTS patch, we unconditionally turn on the NPU regulator as a workaround. I'm pretty sure the issue is with the device trees.

There's something wrong with the `rockchip-pm-domain` device tree config. I'm getting the following errors in `dmesg`: ``` [ 11.023991] rockchip-pm-domain fd8d8000.power-management:power-controller: failed to set domain 'nputop' on, val=0 ``` ``` [ 11.081941] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier 2-0042 for /power-management@fd8d8000/power-controller/power-domain@8 ``` ``` [ 37.865766] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdba4000.video-codec [ 37.865778] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdba8000.video-codec [ 37.865782] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdbac000.video-codec ``` In our [NPU DTS patch](https://git.filchenko.org/dmitriy/rk3588_flake/src/commit/ad109342d4edc7b878b182634454814a27b7755c/cm5_npu_dts.patch#L56), we unconditionally turn on the NPU regulator as a workaround. I'm pretty sure the issue is with the device trees.
dmitriy commented 2025-08-24 16:27:55 -06:00
Author
Owner
Copy link

I see the regulator driver log the following:

[   23.610767] fan53555-regulator 2-0042: FAN53555 Option[10] Rev[1] Detected!
[   23.611098] fan53555-regulator 0-0042: FAN53555 Option[10] Rev[1] Detected!
[   23.612127] fan53555-regulator 0-0043: FAN53555 Option[10] Rev[1] Detected!

We should verify that these are indeed detected as RK860-2s, although I'm pretty certain they are. FAN53555 is the correct driver for these.

I see the regulator driver log the following: ``` [ 23.610767] fan53555-regulator 2-0042: FAN53555 Option[10] Rev[1] Detected! [ 23.611098] fan53555-regulator 0-0042: FAN53555 Option[10] Rev[1] Detected! [ 23.612127] fan53555-regulator 0-0043: FAN53555 Option[10] Rev[1] Detected! ``` We should verify that these are indeed detected as `RK860-2`s, although I'm pretty certain they are. FAN53555 is the correct driver for these.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
justwerkz_resurrections
justwerkz_revolutions
justwerkz_reloaded
justwerkz
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dmitriy/rk3588_flake#1
No description provided.