From: Sean Young <sean@mess.org>
To: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
Cc: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.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 <grant.likely@linaro.org>
Subject: Re: [PATCH v2] media: st-rc: Add ST remote control driver
Date: Thu, 29 Aug 2013 13:01:46 +0100 [thread overview]
Message-ID: <20130829120146.GA7811@pequod.mess.org> (raw)
In-Reply-To: <521F307C.9040807@st.com>
On Thu, Aug 29, 2013 at 12:29:00PM +0100, Srinivas KANDAGATLA wrote:
> On 29/08/13 10:11, Sean Young wrote:
> > On Wed, Aug 28, 2013 at 04:33:50PM +0100, Srinivas KANDAGATLA wrote:
> >> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
> >> +config RC_ST
> >> + tristate "ST remote control receiver"
> >> + depends on ARCH_STI && LIRC && OF
> >
> > Minor nitpick, this should not depend on LIRC, it depends on RC_CORE.
> Yes, I will make it depend on RC_CORE, remove OF as suggested by Mauro
> CC and select LIRC to something like.
>
> depends on ARCH_STI && RC_CORE
> select LIRC
The driver is usable with the kernel ir decoders, there is no need to
select LIRC or use lirc at all.
You can either define a remote in drivers/media/rc/keymaps and set
the rcdev->map_name, or it can be loaded at runtime using ir-keytable(1);
either way you don't need to use a lirc userspace daemon.
Sean
next prev parent reply other threads:[~2013-08-29 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 15:33 [PATCH v2] media: st-rc: Add ST remote control driver Srinivas KANDAGATLA
2013-08-29 9:11 ` Sean Young
2013-08-29 10:49 ` Mauro Carvalho Chehab
2013-08-29 11:30 ` Srinivas KANDAGATLA
2013-08-29 11:29 ` Srinivas KANDAGATLA
2013-08-29 12:01 ` Sean Young [this message]
2013-08-29 11:50 ` 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=20130829120146.GA7811@pequod.mess.org \
--to=sean@mess.org \
--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=mark.rutland@arm.com \
--cc=pawel.moll@arm.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).