From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "Marek Vašut" <marex@denx.de>
Subject: Re: RFC: humidity sensor heaters
Date: Sun, 23 Aug 2015 16:55:37 +0100 [thread overview]
Message-ID: <55D9ECF9.1010303@kernel.org> (raw)
In-Reply-To: <84D8A360-F891-42D6-98A4-7BE289C8B236@gmail.com>
On 23/08/15 08:29, Matt Ranostay wrote:
> That all seems perfectly logical just wanted to be sure what would be the best way.
>
> Would it make sense to block temp reads to raw with the heater on?
> Like what a lot of drivers do on buffered triggered reads for some
> channels
Probably chip dependent (might be well isolated as some of these parts are
quite large). However, if it definitely has a pronounced effect (guessing
it does) then sure. Return -EBUSY if it is enabled and the temperature is
read.
J
>
> Sent from my iPhone
>
>> On Aug 20, 2015, at 20:56, Matt Ranostay <mranostay@gmail.com> wrote:
>>
>> Jonathan et all,
>>
>> So I am currently working on a driver for the TI HDC100x series of
>> temp + humidity sensors, and have a question on how we should handler
>> the heater functionality.
>>
>> This seems quite common in high accuracy relative humidity sensors to
>> have a resistive element within the sensor to heat up the device and
>> get rid of any condensation that happens in a high humidity
>> environment.
>>
>> Now it could be a one off sysfs entry within the driver like
>> "heater_status" but it seems something we want to more generic since
>> this will be an issue in the future (aka si7005 driver for instance).
>>
>> Thoughts? Comments?
>>
>> Thanks,
>>
>> Matt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-08-23 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 3:56 RFC: humidity sensor heaters Matt Ranostay
2015-08-22 17:44 ` Jonathan Cameron
2015-08-23 7:29 ` Matt Ranostay
2015-08-23 15:55 ` Jonathan Cameron [this message]
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=55D9ECF9.1010303@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
--cc=mranostay@gmail.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.