From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-iio@vger.kernel.org, denis.ciocca@st.com,
devicetree-discuss@lists.ozlabs.org, l.czerwinski@samsung.com,
maxime.ripard@free-electrons.com,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2] iio: lps331ap: Add support for DT
Date: Sun, 04 Aug 2013 15:30:12 +0200 [thread overview]
Message-ID: <51FE5764.5090304@metafoo.de> (raw)
In-Reply-To: <51FE4117.3040404@kernel.org>
On 08/04/2013 01:55 PM, Jonathan Cameron wrote:
> On 07/19/13 14:36, Jacek Anaszewski wrote:
>> This patch adds DT support for the lps331ap barometer
>> sensor.
>>
>> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> This makes sense to me and looks similar to that in existing bindings
> hence,
>
> Applied to the togreg branch of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>
> Note I am one of those maintainers who has very limited knowledge of device
> tree so am basing this decision on the 'it looks like existing mappings' rather
> than any deep understanding.
The bindings are not OK.
[...]
>> + - drdy-int-pin : redirect DRDY on pin INT1 (1) or pin INT2 (2) (u8)
This is a vendor specific property, so it needs a vendor prefix. Also
abbreviations are kind of frowned upon for dt property names. So
'st,data-ready-interrupt-pin' is probably a better name.
>> + - interrupt-parent : phandle to the interrupt map subnode
>> + - interrupts : interrupt mapping for LPS331AP interrupt sources:
>> + 2 sources: 0 - data ready, 1 - threshold event
>> + - irq-map : irq sub-node defining interrupt map
>> + (all properties listed below are required):
>> + - #interrupt-cells : should be 1
>> + - #address-cells : should be 0
>> + - #size-cells : should be 0
>> + - interrupt-map : table of entries consisting of three child elements:
>> + - unit_interrupt_specifier - 0 : data ready, 1 : threshold event
>> + - interrupt parent phandle
>> + - parent unit interrupt specifier consisiting of two elements:
>> + - index of the interrupt within the controller
[...]
prev parent reply other threads:[~2013-08-04 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 13:36 [PATCH v2] iio:lps331ap: Add support for DT Jacek Anaszewski
2013-07-19 13:36 ` [PATCH v2] iio: lps331ap: " Jacek Anaszewski
2013-08-04 11:55 ` Jonathan Cameron
2013-08-04 12:00 ` Jonathan Cameron
2013-08-04 12:08 ` Maxime Ripard
2013-08-04 16:22 ` Jonathan Cameron
2013-08-04 13:30 ` Lars-Peter Clausen [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=51FE5764.5090304@metafoo.de \
--to=lars@metafoo.de \
--cc=denis.ciocca@st.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=j.anaszewski@samsung.com \
--cc=jic23@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=l.czerwinski@samsung.com \
--cc=linux-iio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
/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).