On Thu, Apr 16, 2015 at 01:51:43PM +0300, Mika Kahola wrote: > On Thu, 2015-04-16 at 09:02 +0100, Chris Wilson wrote: > > On Thu, Apr 16, 2015 at 10:40:51AM +0300, Mika Kahola wrote: > > > From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > > > > > Rather that extracting the current cdclk freuqncy every time someone > > > wants to know it, cache the current value and use that. VLV/CHV already > > > stored a cached value there so just expand that to cover all platforms. > > > > > > Signed-off-by: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > > > > > V2: Rebased to the latest > > > > > > Signed-off-by: Mika Kahola <mika.kahola@xxxxxxxxx> > > > > Which debugfs file shows this? Do we have one for the similar clock freqs? > > -Chris > > > > I don't think we have one for cdclk. Then again, should we add this to > debugfs? Is it useful to know? Yes, it people have added it to userspace tools. It it derived, or variable state that we may get wrong, or are other calculations dependent on it such that we will want to know its value to check the results? Yes. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
