kernel@xxxxxxxxxxxxxxxx writes: > From: Martin Sperl <kernel@xxxxxxxxxxxxxxxx> > > As the sdram clock is a critical clock to the system > the minimal bcm2835-sdram driver claims (and enables) > this clock and also exposes the corresponding sdram > registers via debugfs. I don't think this is a good solution to the problem you are trying to work around. You're relying on the fact that this driver gets successfully probed before a driver that would -EPROBE_DEFER on a sibling clock, which is not a guarantee. Let's please continue the debugging of clock management on linux-clk.
Attachment:
signature.asc
Description: PGP signature
