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 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? 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) regards, p. > > --- > > drivers/iio/frequency/Kconfig | 10 + > > drivers/iio/frequency/Makefile | 1 + > > drivers/iio/frequency/ds1077.c | 425 +++++++++++++++++++++++++++++++++++ > > include/linux/iio/frequency/ds1077.h | 22 ++ > > 4 files changed, 458 insertions(+) > > create mode 100644 drivers/iio/frequency/ds1077.c > > create mode 100644 include/linux/iio/frequency/ds1077.h > > > [...} > -- Peter Meerwald +43-664-2444418 (mobile) -- 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
