Re: SDHI clock imbalance

> The driver calls pm_runtime_set_active() during ->probe(), which means > genpd's ->runtime_resume() callback isn't invoked during that point. > In other words, the clocks managed by the clock domain isn't enabled > during ->probe() as genpd's doesn't get to run pm_clk_resume() from > its

Re: SDHI clock imbalance

On 2 June 2017 at 10:47, Geert Uytterhoeven wrote: > Hi Wolfram, Ulf, Simon, > > While investigating suspend/resume for the R-Car Gen3 clock driver, I > noticed a clock imbalance for SDHI on Salvator-X. > > After boot: > > # head -2 /sys/kernel/debug/clk/clk_summary >

Re: SDHI clock imbalance

Hi Wolfram, On Fri, Jun 2, 2017 at 11:37 AM, Wolfram Sang wrote: >> While investigating suspend/resume for the R-Car Gen3 clock driver, I >> noticed a clock imbalance for SDHI on Salvator-X. > > Thanks for the heads up! Which branch did you use? > renesas-drivers/master? This

Re: SDHI clock imbalance

Hi Geert, > While investigating suspend/resume for the R-Car Gen3 clock driver, I > noticed a clock imbalance for SDHI on Salvator-X. Thanks for the heads up! Which branch did you use? renesas-drivers/master? This is important since we had quite some refactoring going on lately. Regards,

SDHI clock imbalance

Hi Wolfram, Ulf, Simon, While investigating suspend/resume for the R-Car Gen3 clock driver, I noticed a clock imbalance for SDHI on Salvator-X. After boot: # head -2 /sys/kernel/debug/clk/clk_summary clock enable_cnt prepare_cnt rate accuracy phase