From: "Robin Müller-Bady" <mueller-bady-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Writing I2C Sensor Kernel Modules
Date: Thu, 27 Jun 2013 20:12:57 +0200 [thread overview]
Message-ID: <CACRdhnBAMzjATrftkD4a8LoUfx6quUifTP2R_QHCwcmN1b8e-w@mail.gmail.com> (raw)
In-Reply-To: <51CC52BB.5000302-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Hi,
this iio subsystem is a good hint.
Thank you both very much!
Regards,
Robin
Am 27.06.2013 16:57 schrieb "Sylwester Nawrocki" <s.nawrocki-Sze3O3UU22KIwRZHo2/mJg@public.gmane.orgm>:
>
> Hi,
>
> On 06/27/2013 04:33 PM, Robin Müller-Bady wrote:
> > I have a (architectural design) question about I2C drivers in kernel space.
> > Currently, I'm writing userspace software for using external sensors
> > on an raspberry pi via bcm2835's I2C bus with the help of
> > wiringPi/ioctl, e.g. the barometric pressure with the MPL115A2 sensor.
>
> AFAIK the IIO framework should be use nowadays sensors like this one.
> Unfortunately I'm not aware of any detailed documentation of this
> subsystem. This presentation [1] might be helpful.
>
> I think you could get some help asking on linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> mailing list.
>
> > I now had the idea to write the software directly in kernel space,
> > providing a device, e.g. /dev/mpl115a2, for polling the sensor data.
> > Does this idea fit into the architectural design of the I2C subsystem
> > / the sensors ? Or should code for handling I2C clients stay in
> > userspace?
> > Is there any good documentation for writing such drivers except the
> > kernel Documentation? I found some information in the kernel wiki
> > which is unfortunately not that detailed.
>
> [1] http://tinyurl.com/o6yxwrm
>
> Regards,
> Sylwester
>
prev parent reply other threads:[~2013-06-27 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:33 Writing I2C Sensor Kernel Modules Robin Müller-Bady
[not found] ` <CACRdhnDOKdfFSPKmBZ=BoEfp4Tk3dur539b+eHw_bxm23H0rsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 14:41 ` Peter Meerwald
2013-06-27 14:56 ` Sylwester Nawrocki
[not found] ` <51CC52BB.5000302-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-06-27 18:12 ` Robin Müller-Bady [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=CACRdhnBAMzjATrftkD4a8LoUfx6quUifTP2R_QHCwcmN1b8e-w@mail.gmail.com \
--to=mueller-bady-vytec60ixjuavxtiumwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).