linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [RFC 2/2] IIO : core: Introduce Quaternion types
Date: Wed, 01 Jan 2014 14:50:52 +0000	[thread overview]
Message-ID: <52C42B4C.70403@kernel.org> (raw)
In-Reply-To: <1387901990-3469-2-git-send-email-srinivas.pandruvada@linux.intel.com>



On 24/12/13 16:19, Srinivas Pandruvada wrote:
> Introduced IIO_VAL_QUATERNION and its formatting. Format used here:
> x:y:z:w
> In addition quat_rot is added to the channel type name specification and
> new modifier IIO_MOD_QUATERNION to the list of iio modifiers.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Not that this will want to go in as a precursor in a series with a 
driver implementing it.  Fine to propose it as an RFC but for a final
submission it is preferable to also have an example of it being used!
(immediately deals with the 'what is this for?'  question ;)
> ---
>   drivers/iio/industrialio-core.c | 5 +++++
>   include/linux/iio/types.h       | 3 +++
>   2 files changed, 8 insertions(+)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index f0f2a1a..8b6a2fe 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -69,6 +69,7 @@ static const char * const iio_chan_type_name_spec[] = {
>   	[IIO_ALTVOLTAGE] = "altvoltage",
>   	[IIO_CCT] = "cct",
>   	[IIO_PRESSURE] = "pressure",
> +	[IIO_QUAT_ROT] = "quat_rot",
>   };
This is going to give some interesting naming...

in_quat_rot_quaternion_raw etc aren't exactly clear.

I think it's a channel type rather than a modifier, so
would go with

rotquaternion above and not have a modifier below... Note
the lack of underscore is similar to humidityrelative and
is done to make userspace processing easier by allowing a simple
tokenization based on the underscores.


>
>   static const char * const iio_modifier_names[] = {
> @@ -83,6 +84,7 @@ static const char * const iio_modifier_names[] = {
>   	[IIO_MOD_LIGHT_RED] = "red",
>   	[IIO_MOD_LIGHT_GREEN] = "green",
>   	[IIO_MOD_LIGHT_BLUE] = "blue",
> +	[IIO_MOD_QUATERNION] = "quaternion",
>   };
>
>   /* relies on pairs of these shared then separate */
> @@ -403,6 +405,9 @@ ssize_t iio_format_value(char *buf, unsigned int type, int *vals)
>   		vals[1] = do_div(tmp, 1000000000LL);
>   		vals[0] = tmp;
>   		return sprintf(buf, "%d.%09u\n", vals[0], vals[1]);
> +	case IIO_VAL_QUATERNION:
> +		return sprintf(buf, "%d:%d:%d:%d\n", vals[0], vals[1], vals[2],
> +							vals[3]);
>   	default:
>   		return 0;
>   	}
> diff --git a/include/linux/iio/types.h b/include/linux/iio/types.h
> index 4ac928e..878db0e 100644
> --- a/include/linux/iio/types.h
> +++ b/include/linux/iio/types.h
> @@ -29,6 +29,7 @@ enum iio_chan_type {
>   	IIO_ALTVOLTAGE,
>   	IIO_CCT,
>   	IIO_PRESSURE,
> +	IIO_QUAT_ROT,
>   };
>
>   enum iio_modifier {
> @@ -52,6 +53,7 @@ enum iio_modifier {
>   	IIO_MOD_LIGHT_RED,
>   	IIO_MOD_LIGHT_GREEN,
>   	IIO_MOD_LIGHT_BLUE,
> +	IIO_MOD_QUATERNION,
>   };
>
>   enum iio_event_type {
> @@ -78,6 +80,7 @@ enum iio_event_direction {
>   #define IIO_VAL_INT_PLUS_MICRO 2
>   #define IIO_VAL_INT_PLUS_NANO 3
>   #define IIO_VAL_INT_PLUS_MICRO_DB 4
> +#define IIO_VAL_QUATERNION 5
>   #define IIO_VAL_FRACTIONAL 10
>   #define IIO_VAL_FRACTIONAL_LOG2 11
>
>

  reply	other threads:[~2014-01-01 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24 16:19 [RFC 1/2] IIO : core: Enhance read_raw capability Srinivas Pandruvada
2013-12-24 16:19 ` [RFC 2/2] IIO : core: Introduce Quaternion types Srinivas Pandruvada
2014-01-01 14:50   ` Jonathan Cameron [this message]
2014-01-01 14:45 ` [RFC 1/2] IIO : core: Enhance read_raw capability Jonathan Cameron
2014-01-02 10:32   ` Peter Meerwald
2014-01-11 16:27     ` 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=52C42B4C.70403@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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).