[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1XvOXs-00014Z-6F@stardust.g4.wien.funkfeuer.at>
Date: Mon, 01 Dec 2014 11:49:32 +0100
From: Harald Geyer <harald@...ib.org>
To: Richard Weinberger <richard@....at>
cc: linus.walleij@...aro.org, linux-gpio@...r.kernel.org,
javier.martinez@...labora.co.uk, acourbot@...dia.com,
swarren@...dia.com, jic23@...nel.org, knaack.h@....de,
lars@...afoo.de, pmeerw@...erw.net, linux-iio@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Harald Geyer <lambda@...rdust.g4.wien.funkfeuer.at>
Subject: Re: iio: dht11 broken
Hi Richard!
Richard Weinberger writes:
> Staring with 3.12 gpiolib refuses to set an GPIO used as IRQ into output mode.
> see commit d468bf9e (gpio: add API to be strict about GPIO IRQ usage)
> The dht driver does this and is therefore not functional.
> As the dht11 driver got merged in 3.13 there is a high chance that it
> never worked.
Well, I'm developing on mxs and there it works on 3.13 and 3.14 at least.
(I have it in production using 3.14.18 ATM.)
> Harald, are you aware of this issue?
I got one report about this issue, but couldn't reproduce it yet and
the reporter didn't agree to quoting his messages to kernel mailing lists,
so this has been rather low priority on my todo list. Next plan is to
see if I can reproduce the issue on sunxi (A10).
However anybody able to reproduce this and willing to test patches, would
of course push this up on my todo list.
Any input from gpiolib people about what the proper fix would be in
their opinion, of course is appreciated. I don't think the dht11 driver
is doing anything unreasonable per se, so maybe they can clarify how
the API is intended to be used?
Harald
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists