lkml.org 
[lkml]   [2011]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v4 3/6] clk: introduce the common clock framework
Hi Mike,
> + *
> + * @recalc_rate Recalculate the rate of this clock, by quering hardware
> + * and/or the clock's parent. It is up to the caller to insure
> + * that the prepare_mutex is held across this call. Returns the
> + * calculated rate. Optional, but recommended - if this op is not
> + * set then clock rate will be initialized to 0.
I'm still concerned, if it's NULL, why don't just retrun parent's rate if it has?

Thanks
Richard



\
 
 \ /
  Last update: 2011-12-14 08:53    [W:0.139 / U:1.544 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site