From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Fabien Lahoudere <fabien.lahoudere@collabora.com>,
gwendal@chromium.org, egranata@chromium.org,
kernel@collabora.com, Jonathan Corbet <corbet@lwn.net>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Lee Jones <lee.jones@linaro.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Nick Vaccaro <nvaccaro@chromium.org>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] counter: cros_ec: Add synchronization sensor
Date: Sun, 10 Nov 2019 10:14:08 -0500 [thread overview]
Message-ID: <20191110151408.GB3984@icarus> (raw)
In-Reply-To: <6b50bdff184e6af664b7a61e0a8a2cddc5718f0a.camel@collabora.com>
On Tue, Sep 24, 2019 at 04:20:51PM +0200, Fabien Lahoudere wrote:
> Hi all,
>
> After some discussions and investigation, the timestamp is very
> important for that sync driver.
> Google team uses that timestamp to compare with gyroscope timestamp.
>
> So the important data is timestamp and counter value is useless.
> Just the event of counter increment is important to get a timestamp.
>
> In that case, my idea was to just use an IIO driver with a single
> channel with IIO_TIMESTAMP. We discuss this here and it seems
> controversial.
>
> So my question to Jonathan is if we have a timestamp coming from the EC
> itself, can we consider this timestamp as a good IIO driver?
>
> Any other idea is welcome, however Google team would like to manage
> only IIO drivers if possible.
>
> Thanks
Jonathan,
Should the the timestamp from the EC be introduced as an IIO driver
using IIO_TIMESTAMP?
Since there is no corresponding EC Counter driver in the baseline right
now we don't have a conflict yet. If the EC timestamp is introduced as
an IIO driver then we should make any future EC Counter driver mutually
exclusive with the IIO driver in order to prevent any memory space
conflict. At that point we may deprecate the IIO driver and move the
timestamp functionality to the corresponding Counter driver.
That's assuming someone is interested in the Count component enough to
implement an EC Counter driver; otherwise, the IIO driver will serve
just fine if timestamp is the only data desired from this device.
William Breathitt Gray
next prev parent reply other threads:[~2019-11-10 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 12:41 [PATCH v2 0/1] counter: cros_ec: Add sync sensor driver Fabien Lahoudere
2019-08-23 12:41 ` [PATCH v2 1/1] counter: cros_ec: Add synchronization sensor Fabien Lahoudere
2019-08-24 19:48 ` kbuild test robot
2019-08-26 8:56 ` Jonathan Cameron
2019-08-29 11:10 ` Fabien Lahoudere
2019-09-24 14:20 ` Fabien Lahoudere
2019-09-24 14:52 ` William Breathitt Gray
2019-11-10 15:14 ` William Breathitt Gray [this message]
2019-11-11 11:49 ` Jonathan Cameron
2019-11-12 1:16 ` William Breathitt Gray
2020-04-08 17:10 ` Gwendal Grignou
2020-04-08 17:24 ` William Breathitt Gray
2019-08-29 11:34 ` William Breathitt Gray
2019-09-02 9:40 ` Lee Jones
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=20191110151408.GB3984@icarus \
--to=vilhelm.gray@gmail.com \
--cc=bleung@chromium.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=egranata@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=fabien.lahoudere@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nvaccaro@chromium.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 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).