On Mon, 02 Feb 2015 11:41:40 -0800
Stephen Boyd wrote:
+ trace_clk_unprepare_complete(clk);
> >>clk_core_unprepare(clk->parent);
> > I guess you do not care about the clk_core_unprepare time.
>
> Function trace will handle that?
>
If gcc doesn't inline it.
-- Steve
--
To unsubscribe
On 02/02/15 08:00, Steven Rostedt wrote:
> On Fri, 30 Jan 2015 16:16:11 -0800
> Stephen Boyd wrote:
>
>> It's useful to have tracepoints around operations that change the
>> hardware state so that we can debug clock hardware performance
>> and operations. Four basic types of events are supported:
Quoting Steven Rostedt (2015-02-02 08:00:33)
> On Fri, 30 Jan 2015 16:16:11 -0800
> Stephen Boyd wrote:
>
> > It's useful to have tracepoints around operations that change the
> > hardware state so that we can debug clock hardware performance
> > and operations. Four basic types of events are sup
On Fri, 30 Jan 2015 16:16:11 -0800
Stephen Boyd wrote:
> It's useful to have tracepoints around operations that change the
> hardware state so that we can debug clock hardware performance
> and operations. Four basic types of events are supported: on/off
> events for enable, disable, prepare, unp
It's useful to have tracepoints around operations that change the
hardware state so that we can debug clock hardware performance
and operations. Four basic types of events are supported: on/off
events for enable, disable, prepare, unprepare that only record
an event and a clock name, rate changing
Quoting Stephen Boyd (2014-06-30 18:07:49)
> On 06/30/14 17:52, Steven Rostedt wrote:
> > On Mon, 30 Jun 2014 16:56:39 -0700
> > Stephen Boyd wrote:
> >
> >> @@ -483,10 +486,12 @@ static void clk_unprepare_unused_subtree(struct clk
> >> *clk)
> >> return;
> >>
> >> if (__clk_i
On Mon, 30 Jun 2014 18:07:49 -0700
Stephen Boyd wrote:
> >
> >>if (clk->ops->enable) {
> >>ret = clk->ops->enable(clk->hw);
> >>if (ret) {
> >> @@ -945,6 +965,7 @@ static int __clk_enable(struct clk *clk)
> >>return r
On 06/30/14 17:52, Steven Rostedt wrote:
> On Mon, 30 Jun 2014 16:56:39 -0700
> Stephen Boyd wrote:
>
>> @@ -483,10 +486,12 @@ static void clk_unprepare_unused_subtree(struct clk
>> *clk)
>> return;
>>
>> if (__clk_is_prepared(clk)) {
>> +trace_clk_unprepare(clk);
On Mon, 30 Jun 2014 16:56:39 -0700
Stephen Boyd wrote:
> It's useful to have tracepoints around operations that change the
> hardware state so that we can debug clock hardware performance
> and operations. Three basic types of events are supported: on/off
> events for enable, disable, prepare, un
It's useful to have tracepoints around operations that change the
hardware state so that we can debug clock hardware performance
and operations. Three basic types of events are supported: on/off
events for enable, disable, prepare, unprepare that only record
an event and a clock name, rate changing
10 matches
Mail list logo
