From: Lars-Peter Clausen <lars@metafoo.de>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: add ds1077 programmable oscillator driver
Date: Mon, 24 Jun 2013 19:57:17 +0200 [thread overview]
Message-ID: <51C8887D.4080406@metafoo.de> (raw)
In-Reply-To: <alpine.DEB.2.01.1306241932420.13960@pmeerw.net>
On 06/24/2013 07:47 PM, Peter Meerwald wrote:
> Hello,
>
>> Hm, I wonder where we should draw the line between what should be
>> implemented as a IIO driver and what should be implemented as a clk API
>> driver. This one looks like it actually belongs into the clk framework.
>
> several IIO drivers have overlap with other kernel subsystems
Which is not a necessarily good.
>
> I think the 'line' depends on the intended use/application of the driver,
> not so much on characteristics of the hardware; why do you think it
> belongs to clk?
But the usecase might differ from board to board and that's when you get a
problem. One user wants a clk driver another a IIO driver.
>
> the ds1077 is a small, separate chip which can generate a frequency; using
> IIO I can easily control that frequency from userspace
>
> clk seems to be targetted more at integrated clocksources that get
> activated automatically when needed by other components (maybe I am wrong)
I think there is a userspace consumer for the clk API in the making.
next prev parent reply other threads:[~2013-06-24 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 21:54 [PATCH] iio: add ds1077 programmable oscillator driver Peter Meerwald
2013-06-24 16:47 ` Lars-Peter Clausen
2013-06-24 17:47 ` Peter Meerwald
2013-06-24 17:57 ` Lars-Peter Clausen [this message]
2013-06-29 9:46 ` Jonathan Cameron
2013-06-30 5:48 ` Peter Meerwald
2013-07-02 20:32 ` Jonathan Cameron
2013-07-02 20:49 ` Peter Meerwald
2013-07-02 21:07 ` 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=51C8887D.4080406@metafoo.de \
--to=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.