From: Bastien Nocera <hadess@hadess.net>
To: "K. T." <capellamicro@gmail.com>
Cc: linux-iio@vger.kernel.org, Kevin Tsai <ktsai@capellamicro.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio: add Capella CM3218 ambient light sensor driver.
Date: Thu, 14 Apr 2016 14:16:52 +0200 [thread overview]
Message-ID: <1460636212.5584.3.camel@hadess.net> (raw)
In-Reply-To: <CAHvdCWhHzsuRZ0Kj9BbOSBoCQswR-=vrQErDG9J57yDaE30+2A@mail.gmail.com>
Hey Kevin,
On Wed, 2016-04-13 at 11:44 -0700, K. T. wrote:
> Hi Bastien,
>
> What do you mean "doesn't survive"? Can you read the sensor data or
> data is not change? I use Shuttle XPC desktop to test sensor
> driver. In my environment, suspend/resume works. But,
> hibernate/resume may cause sensor won't update issue. Let me know
> more detail about your issue and I will update driver.
I don't know how I tested it, but it seems to work as expected now. I
tested it by suspending and resuming, and the first time I tested, I
couldn't get any more data out of it, not sure why.
It might have been a problem in iio-sensor-proxy, which is due a clean
up anyway, so let me retract my retraction :)
If anyone has comments about the driver, let me know, and I'll work
with Kevin to get those sorted out.
Cheers
next prev parent reply other threads:[~2016-04-14 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 13:29 [PATCH] iio: add Capella CM3218 ambient light sensor driver Bastien Nocera
2016-04-11 14:19 ` Bastien Nocera
2016-04-13 18:44 ` K. T.
2016-04-14 12:16 ` Bastien Nocera [this message]
2016-04-16 20:20 ` Jonathan Cameron
2016-04-19 10:33 ` Bastien Nocera
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=1460636212.5584.3.camel@hadess.net \
--to=hadess@hadess.net \
--cc=capellamicro@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=ktsai@capellamicro.com \
--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).