On 5/4/2012 3:00 PM, Hennerich, Michael wrote:
Jonathan Cameron wrote on 2012-05-04:
On 5/4/2012 2:31 PM, michael.hennerich@xxxxxxxxxx wrote:
From: Michael Hennerich<michael.hennerich@xxxxxxxxxx>
Before I dive in here too far, let me ask the stupid question.
Whilst I know nothing much about it, why is the kernel's clock framework
unsuitable for this device?
Hi Jonathan,
I think we had a similar discussion before.
The in-kernel clock infrastructure HAVE_CLK<linux/clk.h> is not suitable
since it is designed for SoC like systems.
1) The API is exported by arch and platform code.
2) Data structures differ between the different implementations.
3) Coexistence with other clock providers is by design impossible.
Greetings,
Michael
Does ring a bell now you mention it :) Thanks for the summary. I can
imagine
there may be a suggestion to look at overcoming the above in the long term,
but can't see it being worth while for a small number of parts.
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
