From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: "jic23@kernel.org" <jic23@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH 3/3] iio: frequency: New driver for AD9523 SPI Low Jitter Clock Generator
Date: Fri, 04 May 2012 15:42:10 +0100 [thread overview]
Message-ID: <4FA3EAC2.2080005@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D5917714E797B4F51@LIMKCMBX1.ad.analog.com>
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@analog.com wrote:
>>> From: Michael Hennerich<michael.hennerich@analog.com>
>> 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.
next prev parent reply other threads:[~2012-05-04 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 13:31 [PATCH 1/3] iio: documentation: Add out_altvoltage and friends michael.hennerich
2012-05-04 13:31 ` [PATCH 2/3] iio: documentation: create frequency sub-folder and move dds docs michael.hennerich
2012-05-11 12:34 ` Jonathan Cameron
2012-05-04 13:31 ` [PATCH 3/3] iio: frequency: New driver for AD9523 SPI Low Jitter Clock Generator michael.hennerich
2012-05-04 13:50 ` Jonathan Cameron
2012-05-04 14:00 ` Hennerich, Michael
2012-05-04 14:42 ` Jonathan Cameron [this message]
2012-05-12 18:19 ` Jonathan Cameron
2012-05-14 14:09 ` Michael Hennerich
2012-05-14 17:36 ` Jonathan Cameron
2012-05-11 12:35 ` [PATCH 1/3] iio: documentation: Add out_altvoltage and friends Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA3EAC2.2080005@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.