From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
guenter.roeck@ericsson.com, khali@linux-fr.org,
dmitry.torokhov@gmail.com, broonie@opensource.wolfsonmicro.com,
gregkh@suse.de, alan@lxorguk.ukuu.org.uk, arnd@arndb.de
Subject: Re: [PATCH 1/6] IIO: Core sysfs only support.
Date: Mon, 17 Oct 2011 15:42:23 +0200 [thread overview]
Message-ID: <201110171542.24673.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <1318857381-13787-2-git-send-email-jic23@cam.ac.uk>
Hello Jonathan,
On Monday 17 October 2011 15:16:16 you wrote:
> Add support for simple sysfs only interfaces.
>
> Bulk of patch is concerned with taking struct iio_chan_spec
> arrays and generating all the relevant interfaces from them.
>
> Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
> drivers/Kconfig | 2 +
> drivers/Makefile | 3 +
> drivers/iio/Kconfig | 11 +
> drivers/iio/Makefile | 6 +
> drivers/iio/iio.c | 591
> +++++++++++++++++++++++++++++++++++++++++++++ include/linux/iio/iio.h |
> 250 +++++++++++++++++++
> include/linux/iio/sysfs.h | 68 +++++
> 7 files changed, 931 insertions(+), 0 deletions(-)
>
> [...]
> diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
> new file mode 100644
> index 0000000..5d9a97d
> --- /dev/null
> +++ b/drivers/iio/Kconfig
> @@ -0,0 +1,11 @@
> +#
> +# Industrial I/O subsystem
> +#
> +
> +menuconfig IIO
> + tristate "Industrial I/O support"
> + depends on GENERIC_HARDIRQS
> + help
> + The Industrial input / output subsystem provides a unified
> + framework for many different types of embedded sensor.
> + See Documentation/iio for more information.
I don't know much about iio so I want to read about it. But where does
Documentation/iio come from?
Regards,
Alexander
next prev parent reply other threads:[~2011-10-17 13:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:16 [PATCH 0/6] IIO: Out of staging step 1: The core Jonathan Cameron
2011-10-17 13:16 ` [PATCH 1/6] IIO: Core sysfs only support Jonathan Cameron
2011-10-17 13:42 ` Alexander Stein [this message]
2011-10-17 13:48 ` Jonathan Cameron
2011-10-17 16:27 ` Jonathan Cameron
2011-10-17 13:16 ` [PATCH 2/6] IIO:ADC: max1363 initial import Jonathan Cameron
2011-10-17 13:16 ` [PATCH 3/6] IIO:ADC:ad799x " Jonathan Cameron
2011-10-17 13:16 ` [PATCH 4/6] IIO:light:tsl2563 initial move out of staging Jonathan Cameron
2011-10-17 13:16 ` [PATCH 5/6] IIO:imu:adis16400 partial move from staging Jonathan Cameron
2011-10-17 13:16 ` [PATCH 6/6] IIO: ABI documetation Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2011-11-07 14:52 [PATCH 0/6 V2] IIO: Out of staging step 1: The core jic23
2011-11-07 14:52 ` [PATCH 1/6] IIO: Core sysfs only support jic23
2011-11-11 10:40 ` Michael Hennerich
2012-02-01 15:20 ` Maxime Ripard
2011-09-27 14:29 [RFC PATCH 0/6 V2] IIO: Out of staging step 1: The core Jonathan Cameron
2011-09-27 14:29 ` [PATCH 1/6] IIO: Core sysfs only support 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=201110171542.24673.alexander.stein@systec-electronic.com \
--to=alexander.stein@systec-electronic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=guenter.roeck@ericsson.com \
--cc=jic23@cam.ac.uk \
--cc=khali@linux-fr.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).