On Mon, May 13, 2024 at 02:04:41PM +0200, Jerome Brunet wrote: > > On Sat 11 May 2024 at 14:08, Conor Dooley <conor@xxxxxxxxxx> wrote: > > > [[PGP Signed Part:Undecided]] > > On Fri, May 10, 2024 at 12:08:54PM +0300, Dmitry Rokosov wrote: > >> The 'syspll' PLL is a general-purpose PLL designed specifically for the > >> CPU clock. It is capable of producing output frequencies within the > >> range of 768MHz to 1536MHz. > >> > >> The clock source sys_pll_div16, being one of the GEN clock parents, > >> plays a crucial role and cannot be tagged as "optional". Unfortunately, > >> it was not implemented earlier due to the cpu clock ctrl driver's > >> pending status on the TODO list. > > > > It's fine to not mark it optional in the binding, but it should be > > optional in the driver as otherwise backwards compatibility will be > > broken. Given this is an integral clock driver, sounds like it would > > quite likely break booting on these devices if the driver doesn't treat > > syspll_in as optional. > > A lesson perhaps in describing the hardware entirely, even if the > > drivers don't make use of all the information yet? > > That is nice but it is only possible if/when we have perfect knowledge > of the HW being implemented. I don't know about you, but I rarely get > perfect documentation for HW, let alone a public one. > > Those things are bound to happen as we implement support for the HW and > discover how it works, not to mention the mistakes humans will > inevitably do. If Linux was only supporting perfectly documented HW, it > would not be supporting much of them I suspect. I mean, you can say what you want chief about what you did or didn't know, but there's a line in one of the drivers that was added back when the original driver was that talks about the missing clock, so you can't really act as if there was no knowledge about it. If it hadn't been previously known about and TODO-listed, I would not have made these comments. > Stable API is already hard with ioctl but there, both sides are > perfectly known. That is a fundamental difference with the 'DT ABI' > > Getting it right on day 1, every time Wind your neck in, I don't expect you (or anyone else) to get it right on "day 1, every time". I only expect it to be dealt with in a way that is compatible with the existing devicetree. Thanks, Conor. > - because things are set in stone > afterwards - is unrealistic. As a maintainer, I do spend a > disproportionate amount of time checking the bindings submission because > I know how painful it gets to fix things up down the line. > > Unless I missed the simple solution to this problem, we can expect the > problem keep happening again and again, no matter the number of lessons > learned.
Attachment:
signature.asc
Description: PGP signature
