From: Jonathan Cameron <jic23@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>,
"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: Sun, 28 Jan 2018 09:38:29 +0000 [thread overview]
Message-ID: <20180128093829.1b1d9336@archlinux> (raw)
In-Reply-To: <20180128084003.GA23818@amd>
On Sun, 28 Jan 2018 09:40:03 +0100
Pavel Machek <pavel@ucw.cz> wrote:
> hi!
>
> > > > 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?
> > Not necessarily a byte code to execute on the CPU in the gesture
> > sensor, but a format the code running on that CPU understands the way
> > gestures are formatted.
> > But it can be byte code for some manufacturers, so idea is just pass to
> > the firmware and let it process it an opaque format.
>
> It would be really good to figure out common format for different
> sensors. Otherwise kernel is not providing proper hardware
> abstraction.
>
> Pavel
A common format, if it is byte code, would require in kernel compilers
for the various sensors. Not going to happen.
Common format for everything other than the 'load magic firmware' part
might be doable. As in we can describe what the magic firmware is
doing...
Jonathan
prev parent reply other threads:[~2018-01-28 9:38 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
2018-01-27 22:55 ` Pandruvada, Srinivas
2018-01-28 8:40 ` Pavel Machek
2018-01-28 9:38 ` 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=20180128093829.1b1d9336@archlinux \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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).