From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Eric Nelson <eric@nelint.com>
Cc: linux-media@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
patrice.chotard@st.com, fabf@skynet.be, wsa@the-dreams.de,
heiko@sntech.de, devicetree@vger.kernel.org,
otavio@ossystems.com.br
Subject: Re: [PATCH V2 1/2] rc-core: define a default timeout for drivers
Date: Sat, 3 Oct 2015 11:25:10 -0300 [thread overview]
Message-ID: <20151003112510.54fe2a25@recife.lan> (raw)
In-Reply-To: <1442862524-3694-2-git-send-email-eric@nelint.com>
Em Mon, 21 Sep 2015 12:08:43 -0700
Eric Nelson <eric@nelint.com> escreveu:
> A default timeout value of 100ms is workable for most decoders.
> Declare a constant to help standardize its' use.
I guess the worse case scenario is the NEC protocol:
http://www.sbprojects.com/knowledge/ir/nec.php
with allows a repeat message to be sent on every 110ms. As the
repeat message is 11.25 ms, that would mean a maximum time without
data for 98.75 ms. So, in thesis, 100 ms would be ok. However, IR
timings are not always precise and may affected by the battery charge.
So, I think that a timeout of 100ms is too close to 98.75 and may
cause troubles.
S, IMHO, it is safer to define the default timeout as 125ms.
Regards,
Mauro
>
> Signed-off-by: Eric Nelson <eric@nelint.com>
> ---
> include/media/rc-core.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/media/rc-core.h b/include/media/rc-core.h
> index ec921f6..62c64bd 100644
> --- a/include/media/rc-core.h
> +++ b/include/media/rc-core.h
> @@ -239,6 +239,7 @@ static inline void init_ir_raw_event(struct ir_raw_event *ev)
> memset(ev, 0, sizeof(*ev));
> }
>
> +#define IR_DEFAULT_TIMEOUT MS_TO_NS(100)
> #define IR_MAX_DURATION 500000000 /* 500 ms */
> #define US_TO_NS(usec) ((usec) * 1000)
> #define MS_TO_US(msec) ((msec) * 1000)
next prev parent reply other threads:[~2015-10-03 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 14:00 [PATCH][resend] rc: gpio-ir-recv: allow flush space on idle Eric Nelson
2015-09-14 10:00 ` Sean Young
2015-09-14 14:34 ` Eric Nelson
2015-09-14 14:54 ` Sean Young
2015-09-14 15:05 ` Eric Nelson
2015-09-14 15:35 ` Sean Young
2015-09-21 19:08 ` [PATCH V2 0/2] rc: Add timeout support to gpio-ir-recv Eric Nelson
2015-09-21 19:08 ` Eric Nelson
2015-09-21 19:08 ` [PATCH V2 1/2] rc-core: define a default timeout for drivers Eric Nelson
2015-10-03 14:25 ` Mauro Carvalho Chehab [this message]
2015-10-03 14:52 ` Eric Nelson
2015-10-03 15:18 ` Eric Nelson
2015-09-21 19:08 ` [PATCH V2 2/2] rc: gpio-ir-recv: add timeout on idle Eric Nelson
2015-09-23 13:26 ` Sean Young
2015-09-23 13:52 ` Eric Nelson
2015-09-23 14:07 ` [PATCH V3 " Eric Nelson
2015-09-23 14:26 ` Sean Young
2015-10-03 14:27 ` [PATCH V2 0/2] rc: Add timeout support to gpio-ir-recv Mauro Carvalho Chehab
2015-10-03 15:10 ` Eric Nelson
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=20151003112510.54fe2a25@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@nelint.com \
--cc=fabf@skynet.be \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=otavio@ossystems.com.br \
--cc=patrice.chotard@st.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).