On 03/05/16 20:49, J.D. Schroeder wrote:
On 05/03/2016 12:32 PM, Tero Kristo wrote:
Personally I would not recommend using this clock for any timing sensitive
applications. May I ask why you are interested in the exact clock rate of this
clock anyway?
I'm not interested in using this clock and I'm not sure how anyone would use
this clock outside of the processor. See the inline comment that is part of
the change and the commit message for the change. There is no hint in my
change that this is an exact clock rate. It is a clarifying change to help
others avoid using this clock as a 32 kHz clock (which the current clock name
and frequency imply) and it more accurately represents the actual hardware
behavior.
Imo, if you want to clarify things up, the whole secure_32k_ck should be
removed from linux kernel.
-Tero
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
