From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] misc devices: HC-SRO4 ultrasonic distance driver
Date: Thu, 24 Mar 2016 11:24:20 -0400 [thread overview]
Message-ID: <20160324152420.GA18978@kroah.com> (raw)
In-Reply-To: <56F4016B.2040604@johannesthoma.com>
On Thu, Mar 24, 2016 at 04:02:03PM +0100, Johannes Thoma wrote:
> From 56e8f71c990b92c28a8cb03d859880eab8d06a3d Mon Sep 17 00:00:00 2001
> From: Johannes Thoma <johannes@johannesthoma.com>
> Date: Mon, 21 Mar 2016 22:11:01 +0100
> Subject: [PATCH] HC-SRO4 ultrasonic distance sensor driver
>
> The HC-SRO4 is an ultrasonic distance sensor attached to two GPIO
> pins. The driver is controlled via sysfs and supports an (in theory)
> unlimited number of HC-SRO4 devices.
>
> Unlike user land solutions this driver produces precise results
> even when there is high load on the system. It uses a non-blocking
> interrupt triggered mechanism to record the length of the echo
> signal.
>
> This patch is against the raspberry pi kernel from
> https://github.com/raspberrypi/linux.git hash
> e481b5ceae6c94c7e60f8bb8591cbb362806246e
>
> Note that this patch isn't meant for lkml (yet) see:
> TODO's:
>
> .) Patch against mainline (or whatever kernel it belongs to)
> .) Use IIO layer instead of creating random sysfs entries.
> .) Fill in GPIO device as parent to device_create_with_groups().
> .) Test it with two or more HC-SRO4 devices.
> .) Test it on other hardware than raspberry pi.
> .) Test it with kernel debugging enabled.
>
> Anyway, comments are highly appreciated.
>
> Signed-off-by: Johannes Thoma <johannes@johannesthoma.com>
> ---
> MAINTAINERS | 5 +
> drivers/misc/Kconfig | 11 ++
> drivers/misc/Makefile | 1 +
> drivers/misc/hc-sro4.c | 360
> +++++++++++++++++++++++++++++++++++++++++++++++++
Basic comment, your email client corrupted the patch, wrapping the lines
and putting odd spaces at the front of the patch, making it impossible
to apply. Try using 'git send-email' to fix this up, or fix up your
email client.
Also, your patch should not have the email header up there in it, that's
the sign that something went wrong.
try it again?
thanks
greg k-h
next prev parent reply other threads:[~2016-03-24 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56F3FFF2.40906@johannesthoma.com>
2016-03-24 15:02 ` [PATCH] misc devices: HC-SRO4 ultrasonic distance driver Johannes Thoma
2016-03-24 15:24 ` Greg KH [this message]
2016-05-31 21:05 ` [PATCH] HC-SR04 ultrasonic ranger IIO driver johannes at johannesthoma.com
2016-05-31 21:10 ` Johannes Thoma
2016-05-31 21:35 ` Greg KH
2016-06-01 1:02 ` Valdis.Kletnieks at vt.edu
2016-06-01 14:56 ` Daniel Baluta
2016-03-24 15:52 ` [PATCH] misc devices: HC-SRO4 ultrasonic distance driver Daniel Baluta
2016-03-24 18:15 ` Johannes Thoma
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=20160324152420.GA18978@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).