Am 18.08.19 um 04:29 schrieb Chuanhong Guo: > Hi! > > On Sun, Aug 18, 2019 at 2:06 AM Oleksij Rempel <linux@xxxxxxxxxxxxxxxx> wrote: >>>> SYSC_REG_CPLL_CLKCFG1 register is a clock gate controller. It is used to enable or disable clocks. >>>> Jist wild assumption. All peripheral devices are suing bus clock. >>> >>> This assumption is incorrect. When this patchset is applied in >>> OpenWrt, I asked the author why there's still a fixed clock in >>> mt7621.dtsi, He told me that there's another clock for those unchanged >>> peripherals and he doesn't have time to write a clock provider for it. >> >> Can you please provide a link to this patch or email. > > This discussion is in Chinese and using an IM software so there's no > link available. > >> We have at least 2 know registers: >> SYSC_REG_CPLL_CLKCFG0 - it provides some information about boostrapped >> refclock. PLL and dividers used for CPU and some sort of BUS (AHB?). >> SYSC_REG_CPLL_CLKCFG1 - a banch of gates to enable/disable clocks for >> all or some ip cores. >> What is probably missing is a set of dividers for >> each ip core. From your words it is not document. > > The specific missing part I was referring to, is parent clocks for > every gates. I'm not going to assume this with current openwrt device > tree because some peripherals doesn't have a clock binding at all or > have a dummy one there. Ok, then I do not understand what is the motivation to upstream something what is not nearly ready for use. This code is currently on prototyping phase and you have no information how to make it ready. It means, we cannot expect that this driver will be fixed any time soon. -- Regards, Oleksij _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
