All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, "Hennerich,
	Michael" <Michael.Hennerich@analog.com>
Subject: Re: [PATCH] iio: add ds1077 programmable oscillator driver
Date: Tue, 02 Jul 2013 22:07:01 +0100	[thread overview]
Message-ID: <51D340F5.5020209@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.01.1307022236270.32342@pmeerw.net>

On 07/02/2013 09:49 PM, Peter Meerwald wrote:
> Hello Jonathan,
> 
>>>>>> 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.
>>>
>>> are you referring to this? https://patchwork.kernel.org/patch/2551831/
>>> I'm trying to figure out the status...
>> No idea on this I'm afraid, Lars?
> 
> I've been in contact with the person who proposed above patch (Soren);
> the proposal was rejected and he is not following up on it to get 
> it mainline due to lack of time/interest, it is going to be used in his 
> vendor tree only
I've just had a read of the thread. I can see why he gave up on it given
the resistence.

So what is your usecase for this chip that isn't just providing a clock to
some other on board component? (and hence a case where userspace control is
necessary)

> 
>>>> Just to jump on the end of this conversation, sorry Peter but this one definitely
>>>> looks to me like it belongs clk rather than IIO. If there wasn't a userspace
>>>> API in the making, I'd suggest now was the time to propose one as you
>>>> clearly have an application for one.
>>>
>>> fine; so far no reasons were given
>>> does that mean iio frequency is deprecated?
> 
>> So as you see it is a bit fuzzy at best, and sometimes I find myself deliberating
>> for some time on whether to push a driver in another direction from IIO or not.
>> I agreed to the existing frequency drivers on the basis that they didn't fit well
>> elsewhere, but if there is now a userspace clock interface in the works, perhaps
>> it is time to revisit these.
> 
> thank you for the background information
> 
>>> is there a fundamental difference between hardware supported in iio 
>>> frequency and the ds1077?
> 
>> Not a clear one, no.  The ds1077 to my reading is a very simple example of a programable
>> clock but ultimately I 'think' the other two are similar if more complex beasts with
>> perhaps rather different target uses. Note that whether they should go in IIO has was
>> raised at merge time for them. Honestly I'm more than a little lost in the relevant datasheets. I can verify the code is
> 
> ok, understood
> 
>> If there is a blured edge region where things don't fit in clk but do provide
>> functionality that does, then perhaps we need to do a similar job to iio-hwmon?
>> This might be true for some of the DDS parts which can be used as clocks, but
>> would be a very expensive way of doing that.
> 
> I'll keep looking at clk to see what's going on there (if anything :)
> 
> thanks, regards, p.
> 

      reply	other threads:[~2013-07-02 21:07 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
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 [this message]

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=51D340F5.5020209@kernel.org \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=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.