linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Harald Geyer <harald@ccbib.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: iio: dht11 HW issues
Date: Mon, 09 Jun 2014 13:57:44 +0200	[thread overview]
Message-ID: <5395A138.2030708@metafoo.de> (raw)
In-Reply-To: <E1WtlyB-00012Z-I6@stardust.g4.wien.funkfeuer.at>

On 06/09/2014 12:53 AM, Harald Geyer wrote:
> Hi,
>
> a few month ago I submitted a driver vor DHT11 and DHT22 humidity
> sensors.
>
> Alas at least DHT22 seems to have hardware issues: After a few days
> of operation (reading the sensor once per minute) the sensor seems
> to stop responding entirely and the only way to fix this is to power
> cycle the sensor.
>
> I have tried 3.3 V and 5 V supply and have observed this on at least
> two pieces of hardware, so I'm pretty confident the issue is real.
> The obvious solution is to use an additional gpio line to control
> power for the sensor. Now I'm torn whether to handle this in kernel
> space or user space: Since software using the sysfs ABI doesn't even
> know (and shouldn't need to know) that the humidity values come from
> a DHT22, this clearly should be handled be the kernel driver.
>
> OTOH there probably is an infinite number of algorithms (and HW
> configurations) people might want to use to control power and coming
> up with an ABI that allows implementing any of them, will be a
> challange. Any guidance is appreciated.
>

Yes, this sounds like an issue that should be handled transparently in the 
kernel if possible. If you can detect that the sensor does not respond I'd 
say add code to the kernel driver to issue a reset if that happens.

- Lars

  reply	other threads:[~2014-06-09 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08 22:53 iio: dht11 HW issues Harald Geyer
2014-06-09 11:57 ` Lars-Peter Clausen [this message]
2014-06-19 19:45   ` Harald Geyer

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=5395A138.2030708@metafoo.de \
    --to=lars@metafoo.de \
    --cc=harald@ccbib.org \
    --cc=linux-iio@vger.kernel.org \
    /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).