Hello Thomas! > 29 нояб. 2016 г., в 16:42, Thomas Gleixner <[email protected]> написал(а): > > The frequency change would not only affect the clockevent device, it also > would affect the clocksource. So the patch is incomplete, but see below. Looks like kernel disallow change clocksource and shed_clock rate at runtime. I haven’t found any function for that.
> 29 нояб. 2016 г., в 16:42, Thomas Gleixner <[email protected]> написал(а): > > That's broken and the clk framework should keep the CORE_PERI clock at a > constant rate by reprogramming the divider of the CPU clock. Thank you for the hint. > Assumptions w/o real impact are a perfect reason not to apply that > patch. This want's a proper proof that the global timer really changes and > this hackery is required, which I seriously doubt. It really changes. It changes like it changes for smp-twd. I guess they are driven by same clock CORE_PERI. Thank you for help. Alexander.
