All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] tools: iio: Update iio_event_monitor names
Date: Tue, 15 Mar 2016 22:09:30 +0000	[thread overview]
Message-ID: <56E8881A.6050201@kernel.org> (raw)
In-Reply-To: <1458078891-17859-1-git-send-email-pmeerw@pmeerw.net>

On 15/03/16 21:54, Peter Meerwald-Stadler wrote:
> add recently added channel types and modifiers
> 
> Signed-off-by: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Straight forward so applied to the togreg branch of iio.git.
Pushed out as testing for the autobuilders to ignore it.
Come to think of it, I should suggest that builds of tools are
done for patches that touch them...

Jonathan
> ---
>  tools/iio/iio_event_monitor.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/tools/iio/iio_event_monitor.c b/tools/iio/iio_event_monitor.c
> index d51eb04..90980f5 100644
> --- a/tools/iio/iio_event_monitor.c
> +++ b/tools/iio/iio_event_monitor.c
> @@ -53,6 +53,9 @@ static const char * const iio_chan_type_name_spec[] = {
>  	[IIO_ENERGY] = "energy",
>  	[IIO_DISTANCE] = "distance",
>  	[IIO_VELOCITY] = "velocity",
> +	[IIO_CONCENTRATION] = "concentration",
> +	[IIO_RESISTANCE] = "resistance",
> +	[IIO_PH] = "ph",
>  };
>  
>  static const char * const iio_ev_type_text[] = {
> @@ -102,6 +105,10 @@ static const char * const iio_modifier_names[] = {
>  	[IIO_MOD_WALKING] = "walking",
>  	[IIO_MOD_STILL] = "still",
>  	[IIO_MOD_ROOT_SUM_SQUARED_X_Y_Z] = "sqrt(x^2+y^2+z^2)",
> +	[IIO_MOD_I] = "i",
> +	[IIO_MOD_Q] = "q",
> +	[IIO_MOD_CO2] = "co2",
> +	[IIO_MOD_VOC] = "voc",
>  };
>  
>  static bool event_is_known(struct iio_event_data *event)
> @@ -136,6 +143,9 @@ static bool event_is_known(struct iio_event_data *event)
>  	case IIO_ENERGY:
>  	case IIO_DISTANCE:
>  	case IIO_VELOCITY:
> +	case IIO_CONCENTRATION:
> +	case IIO_RESISTANCE:
> +	case IIO_PH:
>  		break;
>  	default:
>  		return false;
> @@ -174,6 +184,10 @@ static bool event_is_known(struct iio_event_data *event)
>  	case IIO_MOD_WALKING:
>  	case IIO_MOD_STILL:
>  	case IIO_MOD_ROOT_SUM_SQUARED_X_Y_Z:
> +	case IIO_MOD_I:
> +	case IIO_MOD_Q:
> +	case IIO_MOD_CO2:
> +	case IIO_MOD_VOC:
>  		break;
>  	default:
>  		return false;
> 


      reply	other threads:[~2016-03-15 22:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 21:54 [PATCH] tools: iio: Update iio_event_monitor names Peter Meerwald-Stadler
2016-03-15 22:09 ` 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=56E8881A.6050201@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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.