On 20/03/2023 20:59, Frank Li wrote: >> >> The second is a good example - as you can see, there is a choice of >> values, so they are not exactly fixed. >> >>> >>> Such frequency information is necessary. We can put to dts or clock drivers. >> The clock driver >> >> If this is the argument, then the answer is NAK. Sorry, but DTS is not >> for offloading fixed stuff just because you do not want to work on >> drivers. The same for discoverable stuff. >> >>> Become bigger, or dts become bigger. I think the key point is if property to >> descript hardware information. >> >> You have to understand that with your binding you are not allowing to >> any changes of these frequencies. > > Do you means it should be okay if one of clocks is not fixed? We have here long discussion why does your binding require fixed frequencies, because this is something unusual and not recommended. And if they are really fixed, then device driver probably should make the choice of frequencies. > > Previous owner already left nxp. I double checked our documents and scfw source code. > I miss understood a clock SC_PM_CLK_MST_BUS, which actually mapped to IP's aclk, which > ware 100Mhz to 600Mhz. > >> >> Best regards, >> Krzysztof > Best regards, Krzysztof
