From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: "Antti Seppälä" <a.seppala@gmail.com>
Cc: Sean Young <sean@mess.org>,
linux-media@vger.kernel.org, James Hogan <james.hogan@imgtec.com>
Subject: Re: [RFC PATCH 0/4] rc: Adding support for sysfs wakeup scancodes
Date: Tue, 04 Feb 2014 15:54:41 -0200 [thread overview]
Message-ID: <20140204155441.438c7a3c@samsung.com> (raw)
In-Reply-To: <CAKv9HNY7==4H2ZDrmaX+1BcarRAJd7zUE491oQ2ZJZXezpwOAw@mail.gmail.com>
Em Thu, 23 Jan 2014 21:11:09 +0200
Antti Seppälä <a.seppala@gmail.com> escreveu:
> On 23 January 2014 00:01, Mauro Carvalho Chehab <m.chehab@samsung.com> wrote:
> > Not sure if you saw it, but there's already another patchset proposing
> > that, that got submitted before this changeset:
> > https://patchwork.linuxtv.org/patch/21625/
>
> I actually didn't notice that until now. Seems quite a similar kind of
> approach with even more advanced features than what I had in mind
> (namely the scancode filtering and masking).
>
> However it looks like that patchset has the same drawback about not
> knowing which protocol to use for the wakeup scancode as was pointed
> from my patch.
Well, the protocol is important only if there are two or more active
RCs that produce the same IR code on different protocols.
Also, from the sysfs description made by James, it seems clear to me
that the protocol to be used is the current protocol.
I think is an unlikely border case to have some hardware that supports
more than one IR protocols enabled for the wakeup to work, so James
patch looks ok on my eyes.
Also, nothing prevents to add latter a wakeup_filter_protocol sysfs node
to allow to filter the wakeup scancode to a protocol set different than
the one(s) currently enabled.
> I think I'll try to come up with a new patch addressing the comments
> I've seen so far.
I guess I'll merge James approach, as there are a pile of other patches
depending on it. If we need latter to distinguish between current_protocol
and the wakeup one, as I said, a latter patch can add a
"wakeup_filter_protocol" sysfs node to specify it.
Regards,
Mauro
next prev parent reply other threads:[~2014-02-04 17:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 14:18 [PATCH] nuvoton-cir: Add support for user configurable wake-up codes Antti Seppälä
2014-01-15 19:35 ` Mauro Carvalho Chehab
2014-01-20 19:39 ` [RFC PATCH 0/4] rc: Adding support for sysfs wakeup scancodes Antti Seppälä
2014-01-20 19:39 ` [RFC PATCH 1/4] rc-core: Add defintions needed for sysfs callback Antti Seppälä
2014-01-20 19:39 ` [RFC PATCH 2/4] rc-core: Add support for reading/writing wakeup scancodes via sysfs Antti Seppälä
2014-01-20 19:39 ` [RFC PATCH 3/4] rc-loopback: " Antti Seppälä
2014-01-20 19:39 ` [RFC PATCH 4/4] nuvoton-cir: " Antti Seppälä
2014-01-21 12:28 ` [RFC PATCH 0/4] rc: Adding support for sysfs wakeup scancodes Sean Young
2014-01-22 15:46 ` Antti Seppälä
2014-01-22 16:29 ` Sean Young
2014-01-22 19:10 ` Antti Seppälä
2014-01-22 19:21 ` Antti Palosaari
2014-01-22 21:00 ` Sean Young
2014-01-22 22:01 ` Mauro Carvalho Chehab
2014-01-23 19:11 ` Antti Seppälä
2014-02-04 17:54 ` Mauro Carvalho Chehab [this message]
2014-02-05 7:03 ` Antti Seppälä
2014-02-05 9:36 ` Mauro Carvalho Chehab
2014-02-05 9:39 ` James Hogan
2014-02-05 9:42 ` James Hogan
2014-02-05 18:16 ` Antti Seppälä
2014-02-05 21:21 ` Mauro Carvalho Chehab
2014-02-06 10:46 ` James Hogan
2014-02-06 14:55 ` Mauro Carvalho Chehab
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=20140204155441.438c7a3c@samsung.com \
--to=m.chehab@samsung.com \
--cc=a.seppala@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.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