On Thu, Feb 03, 2011 at 09:58:33AM +0000, Hennerich, Michael wrote: > Greg KH wrote on 2011-02-02: > > On Wed, Feb 02, 2011 at 08:36:27PM +0000, Hennerich, Michael wrote: > >> Greg KH wrote on 2011-02-02: > >>> On Wed, Feb 02, 2011 at 08:21:08PM +0100, > >>> michael.hennerich@xxxxxxxxxx > >>> wrote: > >>>> From: Michael Hennerich <michael.hennerich@xxxxxxxxxx> > >>>> > >>>> This patch adds a new trigger that can be invoked by writing the > >>>> sysfs > >>>> file: trigger_now. This approach can be valuable during automated > >>>> testing or in situations, where other trigger methods are not > >>>> applicable. For example no RTC or spare GPIOs. Last but not least > >>>> we can allow user space applications to produce triggers. > >>>> > >>>> Signed-off-by: Michael Hennerich <michael.hennerich@xxxxxxxxxx> > >>>> Acked-by: Jonathan Cameron <jic23@xxxxxxxxx> > >>> > >>> If you add a new sysfs file, you need to document it. I'll not take > >>> this patch as-is because of that. > >>> > >>>> --- > >>>> drivers/staging/iio/trigger/Kconfig | 6 ++ > >>>> drivers/staging/iio/trigger/Makefile | 1 + > >>>> drivers/staging/iio/trigger/iio-trig-sysfs.c | 108 > >>>> ++++++++++++++++++++++++++ 3 files changed, 115 insertions(+), 0 > >>>> deletions(-) create mode > >>>> 100644 drivers/staging/iio/trigger/iio-trig-sysfs.c > >>>> > >>>> diff --git a/drivers/staging/iio/trigger/Kconfig > >>>> b/drivers/staging/iio/trigger/Kconfig > >>>> index d842a58..c185e47 100644 > >>>> --- a/drivers/staging/iio/trigger/Kconfig > >>>> +++ b/drivers/staging/iio/trigger/Kconfig > >>>> @@ -18,4 +18,10 @@ config IIO_GPIO_TRIGGER > >>>> help > >>>> Provides support for using GPIO pins as IIO triggers. > >>>> +config IIO_SYSFS_TRIGGER > >>>> + tristate "SYSFS trigger" > >>>> + depends on SYSFS > >>>> + help > >>>> + Provides support for using SYSFS entry as IIO triggers. > >>> > >>> Why would you ever want to not have this enabled? Why is it a > >>> config option? And shouldn't it depend on the IIO subsystem? > >> > >> You won't see this if you don't have IIO + triggers enabled. > > > > Ok, the dependancy on IIO comes from other parts of the Kconfig file, > > my mistake. > > > >> Are you asking me to add more help text here - or you didn't read the > >> commit log? Alternatively are you asking why IIO common trigger core > >> doesn't provide this flexibility? > >> > >> Sorry - please explain. > > > > My question is, why is this a config option at all? Why would it not > > always be enabled? What benefit is it if it is not enabled? > > It's a config option, since the user must provide a platform resource for > it. What platform resource? > If you're not planning to use it, why compile and include it at all? If you are a distro, how are you supposed to know if this is something you want or not? If this is going to be the proper API for interacting with iio devices, then it needs to always be present in the core, otherwise your userspace tools are going to get messy, right? > In embedded systems, people try to minimize kernel or rootfs size. Sure, and how much size does this code really take? > And last but not least kernel startup time. How much extra time does this module take at startup time that you have measured? I've spent weeks working on boot speedup times for products, and a tiny module like this, built into the kernel, would have no measurable affect on boot time that I can see. What am I missing? thanks, greg k-h -- 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
