From: "Måns Rullgård" <mans@mansr.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Sean Young <sean@mess.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media <linux-media@vger.kernel.org>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>,
Mason <slash.tmp@free.fr>
Subject: Re: [PATCH v1] media: rc: Add driver for tango IR decoder
Date: Tue, 19 Sep 2017 13:21:32 +0100 [thread overview]
Message-ID: <yw1xwp4uyj3n.fsf@mansr.com> (raw)
In-Reply-To: <569e41a9-57c9-3d6f-4157-dffb23f997c6@sigmadesigns.com> (Marc Gonzalez's message of "Tue, 19 Sep 2017 13:53:30 +0200")
Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:
> On 18/09/2017 17:33, Måns Rullgård wrote:
>
>> What have you changed compared to my original code?
>
> I forgot to mention one change you may not approve of, so we should
> probably discuss it.
>
> Your driver supported an optional DT property "linux,rc-map-name"
> to override the RC_MAP_EMPTY map. Since the IR decoder supports
> multiple protocols, I found it odd to specify a scancode map in
> something as low-level as the device tree.
>
> I saw only one board using that property:
> $ git grep "linux,rc-map-name" arch/
> arch/arm64/boot/dts/amlogic/meson-gxl-s905x-khadas-vim.dts: linux,rc-map-name = "rc-geekbox";
>
> So I removed support for "linux,rc-map-name" and used ir-keytable
> to load a given map from user-space, depending on which RC I use.
>
> Mans, Sean, what do you think?
The property is documented as common for IR receivers although only a
few drivers seem to actually implement the feature. Since driver
support is trivial, I see no reason to skip it. Presumably someone
had a use for it, or it wouldn't have been added.
--
Måns Rullgård
next prev parent reply other threads:[~2017-09-19 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:18 [PATCH v1] media: rc: Add driver for tango IR decoder Marc Gonzalez
2017-09-18 15:33 ` Måns Rullgård
2017-09-19 8:45 ` Marc Gonzalez
2017-09-19 9:48 ` Måns Rullgård
2017-09-19 11:34 ` Marc Gonzalez
2017-09-19 11:54 ` Måns Rullgård
2017-09-19 11:53 ` Marc Gonzalez
2017-09-19 12:21 ` Måns Rullgård [this message]
2017-09-19 12:43 ` Marc Gonzalez
2017-09-19 14:32 ` Måns Rullgård
2017-09-21 11:19 ` Sean Young
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=yw1xwp4uyj3n.fsf@mansr.com \
--to=mans@mansr.com \
--cc=linux-media@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
--cc=mchehab@kernel.org \
--cc=sean@mess.org \
--cc=slash.tmp@free.fr \
--cc=thibaud_cornic@sigmadesigns.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