From: Mark Rutland <mark.rutland@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>,
Pawel Moll <Pawel.Moll@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 v3] media: st-rc: Add ST remote control driver
Date: Wed, 18 Sep 2013 15:12:52 +0100 [thread overview]
Message-ID: <20130918141252.GA17453@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <52397C51.1020608@st.com>
On Wed, Sep 18, 2013 at 11:11:29AM +0100, Srinivas KANDAGATLA wrote:
> Thanks Mark,
>
> On 16/09/13 15:10, Mark Rutland wrote:
> >> +
> >> > +Required properties:
> >> > + - compatible: should be "st,comms-irb".
> > This should probably say "should contain" rather than "should be". There
> > may be future vairants of this device, which will also have a more
> > specific compatible string.
> Ok, will change it to the suggest.
> >
> >> > + - 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.
> > I don't like the phrase "interrupt number to the cpu". We already have
> > the term interrupt-specifier to precisely define this. How about:
> >
> > - interrupts: interrupt-specifier for the sole interrupt generated by
> > the device.
> >
> TBH, I did copy them from one of the existing bindings docs.
> I will change it.
There's a lot of inconsistency with existing docs, it would be nice to
use consistent, correct terminology going forward :)
> >> > +
> >> > +Optional properties:
> >> > + - rx-mode: can be "infrared" or "uhf".
> >> > + - tx-mode: should be "infrared".
> > Are these required to use rx/tx?
> Yes, these are required for driver to be in rx/tx mode.
>
> One of them can be optional depending on the board setup.
> So, Is it ok to move such properties to required properties section?
I'd probably just make a note on each stating what they mean (i.e. that
rx-mode should be present iff the rx pins are wired up).
> >
> > If you don't have a tx-mode or rx-mode, I assume you can't do
> > anything...
> Yes, driver errs out.
> >
> >> > + - pinctrl-names, pinctrl-0: the pincontrol settings to configure
> >> > + muxing properly for IRB pins.
> > If we're expecting names, the names we expect should be defined.
> >
> >> > + - clocks : phandle of clock.
> > This is not just a phandle. This is a phandle + clock-specifier pair.
> Yep, will change it.
Cheers.
Mark.
prev parent reply other threads:[~2013-09-18 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 12:06 [PATCH v3] media: st-rc: Add ST remote control driver Srinivas KANDAGATLA
2013-09-16 14:10 ` Mark Rutland
2013-09-18 10:11 ` Srinivas KANDAGATLA
2013-09-18 14:12 ` Mark Rutland [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=20130918141252.GA17453@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@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).