From: Hartmut Knaack <knaack.h@gmx.de>
To: Daniel Baluta <daniel.baluta@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Industrial I/O presentation at LinuxCon Europe
Date: Fri, 9 Oct 2015 23:13:25 +0200 [thread overview]
Message-ID: <56182DF5.2070507@gmx.de> (raw)
In-Reply-To: <CAEnQRZAf3Sp=NrC5S+4pW6=N4kS4cmqbXCesdd7e1b6mfKc-zA@mail.gmail.com>
Daniel Baluta schrieb am 09.10.2015 um 11:06:
> Hi all,
>
> This Monday I presented an introduction to IIO at LinuxCon.
>
> The slides can be found here:
>
> * https://www.overleaf.com/articles/industrial-i-slash-o/dmqjqpzswtvb.pdf
>
> and soon they will be uploaded to Linux foundation site.
>
Awesome. Looks very good overall. But before uploading to Linux foundation,
please consider the following remarks (I hope my brief notes make sense to you):
Page 10: IIO_CHAN_PROCESSED => IIO_CHAN_INFO_PROCESSED
Page 16: temp_channel => accel_channels? fill empty comment, IIO_CPU => IIO_LE?
Page 21: several io => iio, highlighted "enable" in last line intended?
Pages 20 and 25: deprecate terms "top half" and "bottom half" (IIRC there is now
handler [h] for timing critical IRQ handling and thread [th] for uncritical work)?
Thanks,
Hartmut
> I hope this presentation helped people to have an idea about
> what IIO is and how they can start to write drivers for sensors.
>
> Taking in account the number of questions received I think that we'll
> soon see an increase in the number of drivers submitted :).
>
> thanks,
> Daniel.
> --
> 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
>
next prev parent reply other threads:[~2015-10-09 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 9:06 Industrial I/O presentation at LinuxCon Europe Daniel Baluta
2015-10-09 9:17 ` Denis Ciocca
2015-10-09 12:06 ` Crt Mori
2015-10-09 21:13 ` Hartmut Knaack [this message]
2015-10-14 11:22 ` Daniel Baluta
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=56182DF5.2070507@gmx.de \
--to=knaack.h@gmx.de \
--cc=daniel.baluta@gmail.com \
--cc=linux-iio@vger.kernel.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.