From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Userspace event handling and header files
Date: Fri, 21 Oct 2011 09:21:33 +0200 [thread overview]
Message-ID: <4EA11D7D.80202@metafoo.de> (raw)
Hi Jonathan,
I tried to write a small userspace iio event monitor in the style of evtest.
Right now we have four header files for iio: iio_core.h iio.h chrdev.h and
sysfs.h. To be able to receive and probably decode events in userspace we
need three of theses headers: chrdev.h for ioctls and the iio_event_data
struct, sysfs.h for the different iio_event enums and associated macros,
iio.h for the iio_chan_type and iio_modifier enums.
Since we probably don't want to export the sysfs.h and chrdev.h headers to
userspace I propose that we move everything which is needed for external API
into a common header for example iio.h and move all internal API, which is
only required to write a IIO driver for by the core itself, from the iio.h
header to a different header like iio_core.h.
What is your opinion on this?
- Lars
next reply other threads:[~2011-10-21 7:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 7:21 Lars-Peter Clausen [this message]
2011-10-21 8:02 ` Userspace event handling and header files Hennerich, Michael
2011-10-21 8:58 ` Jonathan Cameron
2011-10-21 9:09 ` [PATCH] staging:iio: header reorganization Jonathan Cameron
2011-10-21 9:12 ` Jonathan Cameron
2011-10-21 9:28 ` Jonathan Cameron
2011-10-21 10:42 ` Lars-Peter Clausen
2011-10-21 10:59 ` Jonathan Cameron
2011-10-21 11:15 ` Jonathan Cameron
2011-10-21 10:59 ` [PATCH 1/2] staging:iio: Add missing ioctl.h include to events.h Lars-Peter Clausen
2011-10-21 10:59 ` [PATCH 2/2] staging:iio: Use userspace types for iio_event_data Lars-Peter Clausen
2011-10-21 11:39 ` Jonathan Cameron
2011-10-21 11:00 ` [PATCH 1/2] staging:iio: Add missing ioctl.h include to events.h Jonathan Cameron
2011-10-21 9:42 ` Userspace event handling and header files Lars-Peter Clausen
2011-10-21 9:44 ` Jonathan Cameron
2011-10-21 9:51 ` 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=4EA11D7D.80202@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@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 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.