From: Richard Weinberger <richard@nod.at>
To: Harald Geyer <harald@ccbib.org>
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, sanjeev_sharma@mentor.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: dht11: IRQ fixes
Date: Tue, 02 Dec 2014 11:54:39 +0100 [thread overview]
Message-ID: <547D9A6F.9010801@nod.at> (raw)
In-Reply-To: <E1XvkYl-00013g-VO@stardust.g4.wien.funkfeuer.at>
Harald,
Am 02.12.2014 um 11:19 schrieb Harald Geyer:
> Hi Richard,
>
> thanks for the patch.
>
> I think (haven't tried yet) that your patch changes the number of
> edges recorded per transmission. So probably the decoding function
> needs to be adapted too...
Can you explain your thought?
I'll happily dig into that.
> I won't be able to ACK this before testing on real HW. Of course
> confirmation that your changes work reliably on both DHT11 and DHT22
> will do as well. The debuging code present in the initial submission
> of the driver might be helpful to anybody trying to verify the
> timing.
I have only DHT22 sensors. Of course I've tested the driver with these.
> I'm doing kernel work in my free time and am quite busy with my day job
> right now, so it will take a few days before I can test your code myself.
> Sorry about that.
No need to worry!
Thanks,
//richard
next prev parent reply other threads:[~2014-12-02 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 20:27 [PATCH 1/2] iio: dht11: Add locking Richard Weinberger
2014-12-01 20:27 ` [PATCH 2/2] iio: dht11: IRQ fixes Richard Weinberger
2014-12-02 10:19 ` Harald Geyer
2014-12-02 10:54 ` Richard Weinberger [this message]
2014-12-02 12:58 ` Harald Geyer
2014-12-02 18:12 ` Richard Weinberger
2014-12-02 19:49 ` Harald Geyer
2014-12-02 20:39 ` Richard Weinberger
2014-12-03 20:14 ` Hartmut Knaack
2014-12-02 10:07 ` [PATCH 1/2] iio: dht11: Add locking Harald Geyer
2014-12-02 10:52 ` Richard Weinberger
2014-12-02 12:14 ` Harald Geyer
2014-12-02 17:58 ` Richard Weinberger
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=547D9A6F.9010801@nod.at \
--to=richard@nod.at \
--cc=harald@ccbib.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sanjeev_sharma@mentor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.