linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
Cc: "jic23@kernel.org" <jic23@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [RFP] iio: Support of gesture sensor as a standard IIO sensor
Date: Sat, 27 Jan 2018 23:09:32 +0100	[thread overview]
Message-ID: <20180127220931.GA19668@amd> (raw)
In-Reply-To: <1516480282.15527.4.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

On Sat 2018-01-20 20:31:23, Pandruvada, Srinivas wrote:
> On Sat, 2018-01-20 at 15:19 +0000, Jonathan Cameron wrote:
> > On Thu, 18 Jan 2018 23:40:26 +0100
> > Pavel Machek <pavel@ucw.cz> wrote:
> > 
> > > 
> > > Hi!
> > > 
> > > > 
> > > > From an IIO sensor point of view A Gesture sensor:
> > > > Outputs
> > > > 	A pre defined activity type
> > > > 		WAKE
> > > > 		TILT
> > > > 		GLANCE
> > > > 		PICK_UP
> > > > 		 &
> > > > 		 more
> > > > 
> > > > 	A user defined activity type as "string"  
> > > Pre-defined activities are easy.
> > > 
> > > But what about user-defined activities? We'd really like common
> > > interface across different hardware... 
> > Nasty to handle indeed.   It may be the best we can do initially
> > at least is user_definedN or similar.  No way of constraining
> > users from uploading something really odd that we can't define
> > an interface for (hopping whilst holding a phone in
> > their teeth?)
> That's what I think also. We pre define few USER defined activities
> Ids.

Ok, so this is really device for human interaction -- input device.

> > > > Inputs
> > > > 	A raw binary cdev interface to download templates/patterns  
> > > ....and "raw binary" will not work across different hardware :-(.
> > Sadly there probably isn't much we can do about the format being
> > custom.
> > Best bet would ultimately be if there was at least a standard tool
> > to generate the files for different devices...
> > 
> Correct. This will depend on  the firmware expected format . I think
> ultimately it will be standardized.

Is it fair to say that "expected" format is some kind of bytecode for
CPU in the gesture sensor?

We have similar problem with smart LED devices...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-01-27 22:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06  0:07 [RFP] iio: Support of gesture sensor as a standard IIO sensor Pandruvada, Srinivas
2018-01-06  0:20 ` Alan Cox
2018-01-06 13:12   ` Jonathan Cameron
2018-01-06 17:43     ` Pandruvada, Srinivas
2018-01-18 22:40 ` Pavel Machek
2018-01-20 15:19   ` Jonathan Cameron
2018-01-20 20:31     ` Pandruvada, Srinivas
2018-01-27 22:09       ` Pavel Machek [this message]
2018-01-27 22:55         ` Pandruvada, Srinivas
2018-01-28  8:40           ` Pavel Machek
2018-01-28  9:38             ` 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=20180127220931.GA19668@amd \
    --to=pavel@ucw.cz \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.pandruvada@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).