On Wed, Aug 10, 2022 at 04:40:04PM +0200, Neil Armstrong wrote: > I don't think it's worth adding so much code for this since we already I don't recall the code for clock providers being that hard? They're generally pretty small, some of the ASoC CODEC drivers did something similar. > had an open-coded function which perfectly worked before. Except in the cases it didn't... > I'm perfectly OK to remove the CCF driver for the legacy clock path > and return back to the old open coded calculation since it perfectly > worked and stop using the legacy clock path for new SoCs since it would > never be selected anyway... It does seem better to go the clock provider route TBH. > ... but GX SoCs are broken so it would need an intermediate fix until > I push the refactoring to cleanup all this. I'm trying to figure out if this is actually fixing the problem or just papering over one case where things happened to go badly.
Attachment:
signature.asc
Description: PGP signature
