> > > > > If the clock is enabled when Linux boots, the Linux clock framework *needs* > > > > > to assume the hardware may have been used in previous boot stages, and it should > > > > > not attempt to disable the clock. > > > > > > > > None of the boot loaders we use do this. > > > > > > But the Linux kernel isn't just used by us. It is not uncommon for STB > > > bootloaders to get information from the frontend as part of the boot process. > > > > Okay, this is the clincher. Since we need to support non-standard > > bootloaders, it's difficult to guarantee that the clock will be > > disabled at boot. For this reason, I believe that we can call this a > > critical clock. > That's good news as the STi maintainer already acked and applied the patch. Matters not. That's why we have `git rebase` and `git revert`. ;) -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
