From: Jonathan Cameron <jic23@kernel.org>
To: Daniel Baluta <daniel.baluta@intel.com>, knaack.h@gmx.de
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
irina.tirdea@intel.com, daniel.baluta@inte.com
Subject: Re: [PATCH v4 7/7] iio: event_monitor: Add support for new channel types
Date: Sat, 22 Nov 2014 11:20:43 +0000 [thread overview]
Message-ID: <5470718B.90608@kernel.org> (raw)
In-Reply-To: <1415623535-24337-8-git-send-email-daniel.baluta@intel.com>
On 10/11/14 12:45, Daniel Baluta wrote:
> We have the following testing scenario:
>
> $ insmod iio_dummy_evgen.ko
> $ insmod iio_dummy.ko
>
> ./iio_event_monitor /dev/iio:device0
> Event: time: 1412786467971335337, type: activity(running), channel: 0,
> evtype: thresh, direction: rising
> Event: time: 1412786530792974091, type: activity(walking), channel: 0,
> evtype: thresh, direction: falling
> Event: time: 1412764319184761765, type: steps, channel: 0, evtype: instance
>
> $ echo 1 > /sys/bus/iio/devices/iio_evgen/poke_ev0
> $ echo 2 > /sys/bus/iio/devices/iio_evgen/poke_ev0
> $ echo 3 > /sys/bus/iio/devices/iio_evgen/poke_ev0
>
> Signed-off-by: Irina Tirdea <irina.tirdea@intel.com>
> Signed-off-by: Daniel Baluta <daniel.baluta@intel.com>
Good description and a good patch. Nice series all in all - I like
the approach of adding ABI with dummy driver and tool support before
the hardware driver comes along. Not quite the same from working out
how things will be used in anger, but still a clean way to work.
All applied to the togreg branch of iio.git - pushed out as testing - in
this case for the autobuilders to completely ignore the patch...
Thanks,
Jonathan
> ---
> .../staging/iio/Documentation/iio_event_monitor.c | 23 +++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/Documentation/iio_event_monitor.c b/drivers/staging/iio/Documentation/iio_event_monitor.c
> index 940ed23..def236a 100644
> --- a/drivers/staging/iio/Documentation/iio_event_monitor.c
> +++ b/drivers/staging/iio/Documentation/iio_event_monitor.c
> @@ -49,6 +49,8 @@ static const char * const iio_chan_type_name_spec[] = {
> [IIO_CCT] = "cct",
> [IIO_PRESSURE] = "pressure",
> [IIO_HUMIDITYRELATIVE] = "humidityrelative",
> + [IIO_ACTIVITY] = "activity",
> + [IIO_STEPS] = "steps",
> };
>
> static const char * const iio_ev_type_text[] = {
> @@ -57,6 +59,7 @@ static const char * const iio_ev_type_text[] = {
> [IIO_EV_TYPE_ROC] = "roc",
> [IIO_EV_TYPE_THRESH_ADAPTIVE] = "thresh_adaptive",
> [IIO_EV_TYPE_MAG_ADAPTIVE] = "mag_adaptive",
> + [IIO_EV_TYPE_INSTANCE] = "instance",
> };
>
> static const char * const iio_ev_dir_text[] = {
> @@ -92,6 +95,10 @@ static const char * const iio_modifier_names[] = {
> [IIO_MOD_NORTH_TRUE] = "from_north_true",
> [IIO_MOD_NORTH_MAGN_TILT_COMP] = "from_north_magnetic_tilt_comp",
> [IIO_MOD_NORTH_TRUE_TILT_COMP] = "from_north_true_tilt_comp",
> + [IIO_MOD_RUNNING] = "running",
> + [IIO_MOD_JOGGING] = "jogging",
> + [IIO_MOD_WALKING] = "walking",
> + [IIO_MOD_STILL] = "still",
> };
>
> static bool event_is_known(struct iio_event_data *event)
> @@ -121,6 +128,8 @@ static bool event_is_known(struct iio_event_data *event)
> case IIO_CCT:
> case IIO_PRESSURE:
> case IIO_HUMIDITYRELATIVE:
> + case IIO_ACTIVITY:
> + case IIO_STEPS:
> break;
> default:
> return false;
> @@ -154,6 +163,10 @@ static bool event_is_known(struct iio_event_data *event)
> case IIO_MOD_NORTH_TRUE:
> case IIO_MOD_NORTH_MAGN_TILT_COMP:
> case IIO_MOD_NORTH_TRUE_TILT_COMP:
> + case IIO_MOD_RUNNING:
> + case IIO_MOD_JOGGING:
> + case IIO_MOD_WALKING:
> + case IIO_MOD_STILL:
> break;
> default:
> return false;
> @@ -165,6 +178,7 @@ static bool event_is_known(struct iio_event_data *event)
> case IIO_EV_TYPE_ROC:
> case IIO_EV_TYPE_THRESH_ADAPTIVE:
> case IIO_EV_TYPE_MAG_ADAPTIVE:
> + case IIO_EV_TYPE_INSTANCE:
> break;
> default:
> return false;
> @@ -174,6 +188,7 @@ static bool event_is_known(struct iio_event_data *event)
> case IIO_EV_DIR_EITHER:
> case IIO_EV_DIR_RISING:
> case IIO_EV_DIR_FALLING:
> + case IIO_EV_DIR_NONE:
> break;
> default:
> return false;
> @@ -214,9 +229,11 @@ static void print_event(struct iio_event_data *event)
> else if (chan >= 0)
> printf("channel: %d, ", chan);
>
> - printf("evtype: %s, direction: %s\n",
> - iio_ev_type_text[ev_type],
> - iio_ev_dir_text[dir]);
> + printf("evtype: %s", iio_ev_type_text[ev_type]);
> +
> + if (dir != IIO_EV_DIR_NONE)
> + printf(", direction: %s", iio_ev_dir_text[dir]);
> + printf("\n");
> }
>
> int main(int argc, char **argv)
>
prev parent reply other threads:[~2014-11-22 11:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:45 [PATCH v4 0/7] Introduce IIO interface for Android advanced features Daniel Baluta
2014-11-10 12:45 ` [PATCH v4 1/7] iio: dummy: Add virtual registers for dummy device Daniel Baluta
2014-11-22 11:06 ` Jonathan Cameron
2014-11-10 12:45 ` [PATCH v4 2/7] iio: core: Introduce IIO_ACTIVITY channel Daniel Baluta
2014-11-22 11:13 ` Jonathan Cameron
2014-11-10 12:45 ` [PATCH v4 3/7] iio: core: Introduce IIO_EV_DIR_NONE Daniel Baluta
2014-11-22 11:13 ` Jonathan Cameron
2014-11-10 12:45 ` [PATCH v4 4/7] iio: core: Introduce STEPS channel, ENABLE mask and INSTANCE event Daniel Baluta
2014-11-22 11:16 ` Jonathan Cameron
2014-11-10 12:45 ` [PATCH v4 5/7] iio: core: Introduce IIO_CHAN_INFO_CALIBHEIGHT Daniel Baluta
2014-11-22 11:17 ` Jonathan Cameron
2014-11-10 12:45 ` [PATCH v4 6/7] iio: dummy: Demonstrate the usage of new channel types Daniel Baluta
2014-11-22 11:05 ` Jonathan Cameron
2014-11-22 11:18 ` Jonathan Cameron
2014-11-24 12:31 ` Daniel Baluta
2014-11-10 12:45 ` [PATCH v4 7/7] iio: event_monitor: Add support for " Daniel Baluta
2014-11-22 11:20 ` Jonathan Cameron [this message]
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=5470718B.90608@kernel.org \
--to=jic23@kernel.org \
--cc=daniel.baluta@inte.com \
--cc=daniel.baluta@intel.com \
--cc=irina.tirdea@intel.com \
--cc=knaack.h@gmx.de \
--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).