5 Apr
2023
5 Apr
'23
5:09 p.m.
On Tue, Apr 04, 2023 at 12:11:53PM +0200, Maxime Ripard wrote:
The driver does implement round_rate() though, which means that we can change the rate of the clock, but we will never get to change the parent.
However, It's hard to tell whether it's been done on purpose or not.
Since we'll start mandating a determine_rate() implementation, let's convert the round_rate() implementation to a determine_rate(), which will also make the current behavior explicit. And if it was an oversight, the clock behaviour can be adjusted later on.
Similar comments to the other patch, I'm pretty sure this is just surprising design on the part of the clock API and we should just allow reparenting.