From: Lars-Peter Clausen <lars@metafoo.de>
To: Johannes Thoma <johannes@johannesthoma.com>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] HC-SR04 ultrasonic ranger IIO driver
Date: Fri, 10 Jun 2016 09:50:02 +0200 [thread overview]
Message-ID: <575A712A.6060606@metafoo.de> (raw)
In-Reply-To: <3fd11d4e-54c4-1589-f0ce-14554bb041c4@johannesthoma.com>
On 06/10/2016 07:35 AM, Johannes Thoma wrote:
> Hi,
>
> Am 07.06.16 um 17:19 schrieb Lars-Peter Clausen:
>>
>> Any new ABI needs to be documented in Documentation/ABI/...
>>
> I will move it there thanks for pointing that out.
>
>> But to take one thing ahead passing the GPIO number (or a label) from
>> userspace is not really a good ABI in my opinion. The GPIO numbers should
>> come from the hardware description (DTS, ACPI, board file, ...)
>>
> I wanted to offer the possibility to configure the device at run time. Since
> it is not part of the board but a periphial device it could also be attached
> while the system is running. I would like to keep this interface but will
> add support for also configue it via device tree, as you suggested.
The right interface for handling re-configurable logic is devicetree
overlays. It allows you to describe the hardware using standard devicetree
descriptions but it can be loaded and unloaded on-demand at runtime.
next prev parent reply other threads:[~2016-06-10 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 18:40 [PATCH] HC-SR04 ultrasonic ranger IIO driver johannes
2016-06-07 5:42 ` Matt Ranostay
2016-06-07 11:44 ` Crt Mori
2016-06-07 15:19 ` Lars-Peter Clausen
2016-06-10 5:35 ` Johannes Thoma
2016-06-10 7:50 ` Lars-Peter Clausen [this message]
2016-06-11 15:20 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2016-03-24 15:24 [PATCH] misc devices: HC-SRO4 ultrasonic distance driver Greg KH
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
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=575A712A.6060606@metafoo.de \
--to=lars@metafoo.de \
--cc=johannes@johannesthoma.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.