From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756716AbeATUba (ORCPT ); Sat, 20 Jan 2018 15:31:30 -0500 Received: from mga09.intel.com ([134.134.136.24]:64392 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756578AbeATUbY (ORCPT ); Sat, 20 Jan 2018 15:31:24 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,387,1511856000"; d="scan'208";a="24985129" From: "Pandruvada, Srinivas" To: "pavel@ucw.cz" , "jic23@kernel.org" CC: "linux-kernel@vger.kernel.org" , "linux-iio@vger.kernel.org" Subject: Re: [RFP] iio: Support of gesture sensor as a standard IIO sensor Thread-Topic: [RFP] iio: Support of gesture sensor as a standard IIO sensor Thread-Index: AQHThoJS7XJRQttGPUOyTnKghZ+zH6N608IAgAKpXQCAAFc9AA== Date: Sat, 20 Jan 2018 20:31:23 +0000 Message-ID: <1516480282.15527.4.camel@intel.com> References: <1515197240.26317.65.camel@intel.com> <20180118224026.GE17196@amd> <20180120151908.1d438aaf@archlinux> In-Reply-To: <20180120151908.1d438aaf@archlinux> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.125.4] Content-Type: text/plain; charset="utf-8" Content-ID: <8223C3F8A8B31B4387652972F109405B@intel.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id w0KKVZJC019760 On Sat, 2018-01-20 at 15:19 +0000, Jonathan Cameron wrote: > On Thu, 18 Jan 2018 23:40:26 +0100 > Pavel Machek 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. > > > > > > > > > > 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. Thanks, Srinivas > > > > > > > > Pavel