From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dylan Howey <Dylan.Howey@tennantco.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
<linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: accel: mma8452: Expose temperature channel
Date: Mon, 17 Feb 2020 18:16:13 +0000 [thread overview]
Message-ID: <20200217181613.000057d2@Huawei.com> (raw)
In-Reply-To: <20200217141902.GA31535@tennantco.com>
On Mon, 17 Feb 2020 08:19:08 -0600
Dylan Howey <Dylan.Howey@tennantco.com> wrote:
> On 02/14/2020 13:24, Jonathan Cameron wrote:
> > So ideally we'd get someone at Freescale to confirm there is a hardware
> > rather than a documentation issue (i.e. maybe we need some other magic).
> I'll try that route first. I have an NXP contact.
>
> > If they do we probably need to avoid breaking them so would need a module
> > parameter to be 'enable temp' rather than the more natural option
> > of 'disable temp' to be set only by people who need the highest
> > frequency.
> That's what I had in mind.
>
> > The question is whether anyone actually cares about 800Hz?
> I have a use case for this. I'm doing some data logging with this hardware
> and a higher sample rate is always better.
>
> By the way, this hardware has a fifo that the driver isn't using. I might
> add support for that. Currently I'm trying to log and getting hammered with
> an 800Hz interrupt and that is causing some issues.
Yeah. Those sorts of rates tend to get tricky without using hardware
fifos. Great if you can add support.
Thanks,
Jonathan
>
next prev parent reply other threads:[~2020-02-17 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 20:32 [PATCH] iio: accel: mma8452: Expose temperature channel Dylan Howey
2020-02-08 16:32 ` Jonathan Cameron
2020-02-10 14:26 ` Dylan Howey
2020-02-13 22:04 ` Dylan Howey
2020-02-14 13:24 ` Jonathan Cameron
2020-02-17 14:19 ` Dylan Howey
2020-02-17 18:16 ` Jonathan Cameron [this message]
2020-02-24 21:00 ` Dylan Howey
2020-03-07 11:20 ` 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=20200217181613.000057d2@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Dylan.Howey@tennantco.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.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).