On Tue, Oct 15, 2013 at 01:11:49PM +0300, Ville Syrjälä wrote:
> On Tue, Oct 15, 2013 at 10:43:31AM +0200, Daniel Vetter wrote:
> > On Fri, Oct 11, 2013 at 04:40:24PM -0300, Paulo Zanoni wrote:
> > > 2013/10/9 :
> > > > From: Ville Syrjälä
> > > >
> > > > We may want to know what kind of watermar
On Tue, Oct 15, 2013 at 10:43:31AM +0200, Daniel Vetter wrote:
> On Fri, Oct 11, 2013 at 04:40:24PM -0300, Paulo Zanoni wrote:
> > 2013/10/9 :
> > > From: Ville Syrjälä
> > >
> > > We may want to know what kind of watermarks got computed and programmed
> > > into the hardware. Using tracepoints i
On Fri, Oct 11, 2013 at 04:40:24PM -0300, Paulo Zanoni wrote:
> 2013/10/9 :
> > From: Ville Syrjälä
> >
> > We may want to know what kind of watermarks got computed and programmed
> > into the hardware. Using tracepoints is much leaner than debug prints.
> >
> > Also add trace call for the waterm
2013/10/9 :
> From: Ville Syrjälä
>
> We may want to know what kind of watermarks got computed and programmed
> into the hardware. Using tracepoints is much leaner than debug prints.
>
> Also add trace call for the watermark state we read out of the
> hardware during init, though I;m not sure the
From: Ville Syrjälä
We may want to know what kind of watermarks got computed and programmed
into the hardware. Using tracepoints is much leaner than debug prints.
Also add trace call for the watermark state we read out of the
hardware during init, though I;m not sure there's any way to see that
