From: Sean Young <sean@mess.org>
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>, Andy Duan <fugang.duan@nxp.com>
Subject: Re: [PATCH] media: rc: gpio-ir-recv: add QoS support for cpuidle system
Date: Wed, 16 Sep 2020 19:19:54 +0100 [thread overview]
Message-ID: <20200916181954.GA27005@gofer.mess.org> (raw)
In-Reply-To: <DB8PR04MB679586E9818080C0ED804848E6210@DB8PR04MB6795.eurprd04.prod.outlook.com>
Hi Joakim,
On Wed, Sep 16, 2020 at 10:22:11AM +0000, Joakim Zhang wrote:
>
> Hi Sean,
>
> Thanks for your hint, I will send a V2 soon according to your suggestions.
>
> We also have a concern, since you are a IR expert, may you can give us answers. With this patch, the first frame once press could not been decoded.
> AFAIK, IR protocols have not specify how may frames transmitting once press, is there ang criterion to decide this?
>
> Is it possible that single frame transmitting once pressing? Per my understanding, it will transmit more than one frame.
So remotes send IR signals while a button is being pressed down. For the
remotes I've seen, when pressing a button a short amount of time will repeat
the IR message at least three times. This is a few times when I've tried
this, but by no means exhaustive of all remotes or protocols.
I think the question you are trying to answer is, if we miss the first
message, will we at least have another chance if the message is repeated?
So I think the message will be repeated, but the repeat message is not
enough for the nec protocol. The nec repeat is a shorter message which
does not carry any information apart from "last key still pressed":
https://www.sbprojects.net/knowledge/ir/nec.php
Thanks,
Sean
next prev parent reply other threads:[~2020-09-16 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 15:02 [PATCH] media: rc: gpio-ir-recv: add QoS support for cpuidle system Joakim Zhang
2020-09-15 9:33 ` Sean Young
2020-09-15 10:55 ` Joakim Zhang
2020-09-15 20:19 ` Sean Young
2020-09-16 10:22 ` Joakim Zhang
2020-09-16 18:19 ` Sean Young [this message]
2020-09-17 9:12 ` Joakim Zhang
2020-09-17 20:43 ` Sean Young
2020-09-18 1:42 ` Joakim Zhang
2020-09-18 8:23 ` Sean Young
2020-09-18 8:56 ` Joakim Zhang
[not found] ` <CAHp75Vftg3GmBsCCrZeXo4eofOYTJ2ii+s64hY5FqZadvX6Bww@mail.gmail.com>
[not found] ` <DB8PR04MB6795840F4C0D938A14D1E3BEE6200@DB8PR04MB6795.eurprd04.prod.outlook.com>
2020-09-15 10:42 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2020-09-15 14:57 Joakim Zhang
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=20200916181954.GA27005@gofer.mess.org \
--to=sean@mess.org \
--cc=fugang.duan@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiangqing.zhang@nxp.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