Hi, On Fri, Sep 13, 2024 at 01:59:10PM GMT, Ulf Hansson wrote: > On Tue, 10 Sept 2024 at 20:05, Sebastian Reichel > <sebastian.reichel@xxxxxxxxxxxxx> wrote: > > I got a report, that the Linux kernel crashes on Rock 5B when the panthor > > driver is loaded late after booting. The crash starts with the following > > shortened error print: > > > > rockchip-pm-domain fd8d8000.power-management:power-controller: failed to set domain 'gpu', val=0 > > rockchip-pm-domain fd8d8000.power-management:power-controller: failed to get ack on domain 'gpu', val=0xa9fff > > SError Interrupt on CPU4, code 0x00000000be000411 -- SError > > > > This series first does some cleanups in the Rockchip power domain > > driver and changes the driver, so that it no longer tries to continue > > when it fails to enable a domain. This gets rid of the SError interrupt > > and long backtraces. But the kernel still hangs when it fails to enable > > a power domain. I have not done further analysis to check if that can > > be avoided. > > > > Last but not least this provides a fix for the GPU power domain failing > > to get enabled - after some testing from my side it seems to require the > > GPU voltage supply to be enabled. > > > > I'm not really happy about the hack to get a regulator for a sub-node > > in the 5th patch, which I took over from the Mediatek driver. But to > > get things going and open a discussion around it I thought it would be > > best to send a first version as soon as possible. > > That creates a circular dependency from the fw_devlink point of view. Yes. > I assume that isn't a problem and fw_devlink takes care of this, so > the GPU power domain still can probe? This has been tested on Radxa Rock 5B and RK3588 EVB1. It properly probes the GPU power domain and fixes late probing of the GPU driver :) > Other than this, I think this looks okay to me. I will send a V2 with the minor things pointed out. Greetings, -- Sebastian
Attachment:
signature.asc
Description: PGP signature
