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: Wed, 28 Aug 2013 19:08:42 -0400 [thread overview]
Message-ID: <87fvtt4dmt.fsf@jerows.sfl> (raw)
In-Reply-To: <521E7CA7.5060407@snapithd.com> (Chris Rodley's message of "Thu, 29 Aug 2013 10:41:43 +1200")
Chris Rodley <chris@snapithd.com> writes:
> Hi,
>
> I am trying to get a sht75 humidity and temperature sensor working
> with the linux kernel module in 3.2.
> Is there a code example for application code that you have available?
>
> Many thanks,
Hi Chris,
There was much less support for the sht15 back in 3.2 compared to recent
kernel releases. You may want to backport features and/or fixes to suit
your needs.
You can find a usage example for 3.2 in arch/arm/mach-pxa/stargate2.c
around line 140:
First, create a platform data struct and specify which GPIO lines are
hooked to the data and sck lines of your sht-15:
static struct sht15_platform_data platform_data_sht15 = {
.gpio_data = 100,
.gpio_sck = 98,
};
Then setup a platform device referencing those platform data, that you
will have to register on the platform bus using platform_add_devices()
or equivalent:
static struct platform_device sht15 = {
.name = "sht15",
.id = -1,
.dev = {
.platform_data = &platform_data_sht15,
},
};
...
platform_add_devices(...);
Cheers,
--
Jérôme Oufella
@: jerome.oufella@savoirfairelinux.com
T: 514-276-5468 ext. 125
next parent reply other threads:[~2013-08-28 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <521E7CA7.5060407@snapithd.com>
2013-08-28 23:08 ` Jerome Oufella [this message]
2013-08-29 3:18 ` sht15 kernel driver Chris Rodley
2013-08-29 15:02 ` Jerome Oufella
2013-08-29 15:28 ` [lm-sensors] " Guenter Roeck
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=87fvtt4dmt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox