On Tue, Jan 4, 2011 at 7:54 PM, Amit Kucheria wrote:
> On Tue, Jan 4, 2011 at 3:16 PM, Yong Shen wrote:
>
In the last several weeks, Jeremy and I reviewed the clock debug code
based on common clock struct. In this code, I used below code to
expose clock information:
On Tue, Jan 4, 2011 at 3:16 PM, Yong Shen wrote:
>>> In the last several weeks, Jeremy and I reviewed the clock debug code
>>> based on common clock struct. In this code, I used below code to
>>> expose clock information:
>>>
>>>
>>> +static int clk_debug_rate_get(void *data, u64 *val)
>>> +{
>>>
On Tue, Jan 4, 2011 at 5:45 PM, Vincent Guittot
wrote:
> On 4 January 2011 09:58, Amit Kucheria wrote:
>> CC'ing linaro-dev
>>
>> On Tue, Jan 4, 2011 at 1:18 PM, Yong Shen wrote:
>>> hi there,
>>>
>>> In last weekly meeting, we talked about the real time display of clock
>>> information in power
Hi Amit,
Please find out inline feedback.
On Tue, Jan 4, 2011 at 4:58 PM, Amit Kucheria wrote:
> CC'ing linaro-dev
>
> On Tue, Jan 4, 2011 at 1:18 PM, Yong Shen wrote:
>> hi there,
>>
>> In last weekly meeting, we talked about the real time display of clock
>> information in powerdebug.
>
> Wha
On 4 January 2011 09:58, Amit Kucheria wrote:
> CC'ing linaro-dev
>
> On Tue, Jan 4, 2011 at 1:18 PM, Yong Shen wrote:
>> hi there,
>>
>> In last weekly meeting, we talked about the real time display of clock
>> information in powerdebug.
>
> What do you mean by real-time display?
>
> powerdebug
CC'ing linaro-dev
On Tue, Jan 4, 2011 at 1:18 PM, Yong Shen wrote:
> hi there,
>
> In last weekly meeting, we talked about the real time display of clock
> information in powerdebug.
What do you mean by real-time display?
powerdebug will only refresh it's information every 'n' seconds. At
that
