From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-232.synserver.de ([212.40.185.232]:1185 "EHLO smtp-out-231.synserver.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752471Ab3FXR44 (ORCPT ); Mon, 24 Jun 2013 13:56:56 -0400 Message-ID: <51C8887D.4080406@metafoo.de> Date: Mon, 24 Jun 2013 19:57:17 +0200 From: Lars-Peter Clausen MIME-Version: 1.0 To: Peter Meerwald CC: linux-iio@vger.kernel.org Subject: Re: [PATCH] iio: add ds1077 programmable oscillator driver References: <1371938043-3865-1-git-send-email-pmeerw@pmeerw.net> <51C87806.5000700@metafoo.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org 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.