From: Pawel Moll <pawel.moll@arm.com>
To: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ian.campbell@citrix.com>,
Rob Landley <rob@landley.net>,
"grant.likely@linaro.org" <grant.likely@linaro.org>
Subject: Re: [PATCH] media: st-rc: Add ST remote control driver
Date: Thu, 15 Aug 2013 14:30:38 +0100 [thread overview]
Message-ID: <1376573438.18617.44.camel@hornet> (raw)
In-Reply-To: <1376501221-22416-1-git-send-email-srinivas.kandagatla@st.com>
On Wed, 2013-08-14 at 18:27 +0100, Srinivas KANDAGATLA wrote:
> +Device-Tree bindings for ST IR and UHF receiver
> +
> +Required properties:
> + - compatible: should be "st,rc".
> + - st,uhfmode: boolean property to indicate if reception is in UHF.
> + - reg: base physical address of the controller and length of memory
> + mapped region.
> + - interrupts: interrupt number to the cpu. The interrupt specifier
> + format depends on the interrupt controller parent.
> +
> +Example node:
> +
> + rc: rc@fe518000 {
> + compatible = "st,rc";
> + reg = <0xfe518000 0x234>;
> + interrupts = <0 203 0>;
> + };
So is "st,uhfmode" required or optional after all? If the former, the
example is wrong (doesn't specify required property). But as far as I
understand it's really optional...
Paweł
next prev parent reply other threads:[~2013-08-15 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 17:27 [PATCH] media: st-rc: Add ST remote control driver Srinivas KANDAGATLA
2013-08-15 8:49 ` Mark Rutland
2013-08-15 12:57 ` Srinivas KANDAGATLA
2013-08-15 13:29 ` Mark Rutland
2013-08-15 14:06 ` Srinivas KANDAGATLA
2013-08-15 14:45 ` Mark Rutland
2013-08-15 13:30 ` Pawel Moll [this message]
2013-08-15 13:23 ` Srinivas KANDAGATLA
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=1376573438.18617.44.camel@hornet \
--to=pawel.moll@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=srinivas.kandagatla@st.com \
--cc=swarren@wwwdotorg.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).