From: Jerome Oufella <jerome.oufella@savoirfairelinux.com>
To: Chris Rodley <chris@snapithd.com>
Cc: kernel@savoirfairelinux.com, linux-kernel@vger.kernel.org,
lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] sht15 kernel driver
Date: Thu, 29 Aug 2013 15:02:16 +0000 [thread overview]
Message-ID: <87ppswh75z.fsf@jerows.sfl> (raw)
In-Reply-To: <521EBD9F.7070502@snapithd.com> (Chris Rodley's message of "Thu, 29 Aug 2013 15:18:55 +1200")
Chris Rodley <chris@snapithd.com> writes:
> Thanks Jerome!
>
> That was just what I needed to know.
> The device is now set up and is working well - I will have a go at
> back porting now.
>
> Many thanks again for your help!
> Chris
Good to know Chris!
Note, we noticed that the sht15 driver may be sensible to noisy lines,
we suspect a race condition around the interrupt handling code.
If your sensor is populated on the board you shouldn't have problems
though.
Jerome
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Oufella <jerome.oufella@savoirfairelinux.com>
To: Chris Rodley <chris@snapithd.com>
Cc: kernel@savoirfairelinux.com, linux-kernel@vger.kernel.org,
lm-sensors@lm-sensors.org
Subject: Re: sht15 kernel driver
Date: Thu, 29 Aug 2013 11:02:16 -0400 [thread overview]
Message-ID: <87ppswh75z.fsf@jerows.sfl> (raw)
In-Reply-To: <521EBD9F.7070502@snapithd.com> (Chris Rodley's message of "Thu, 29 Aug 2013 15:18:55 +1200")
Chris Rodley <chris@snapithd.com> writes:
> Thanks Jerome!
>
> That was just what I needed to know.
> The device is now set up and is working well - I will have a go at
> back porting now.
>
> Many thanks again for your help!
> Chris
Good to know Chris!
Note, we noticed that the sht15 driver may be sensible to noisy lines,
we suspect a race condition around the interrupt handling code.
If your sensor is populated on the board you shouldn't have problems
though.
Jerome
next prev parent reply other threads:[~2013-08-29 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <521E7CA7.5060407@snapithd.com>
2013-08-28 23:08 ` [lm-sensors] sht15 kernel driver Jerome Oufella
2013-08-28 23:08 ` Jerome Oufella
2013-08-29 3:18 ` [lm-sensors] " Chris Rodley
2013-08-29 3:18 ` Chris Rodley
2013-08-29 15:02 ` Jerome Oufella [this message]
2013-08-29 15:02 ` Jerome Oufella
2013-08-29 15:28 ` [lm-sensors] " Guenter Roeck
2013-08-29 15:28 ` Guenter Roeck
2013-08-29 21:58 ` Chris Rodley
2013-08-29 21:58 ` Chris Rodley
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=87ppswh75z.fsf@jerows.sfl \
--to=jerome.oufella@savoirfairelinux.com \
--cc=chris@snapithd.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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 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.