devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/2] rc: Add timeout support to gpio-ir-recv
Date: Sat, 3 Oct 2015 11:27:12 -0300	[thread overview]
Message-ID: <20151003112712.4f54925d@recife.lan> (raw)
In-Reply-To: <1442862524-3694-1-git-send-email-eric@nelint.com>

Em Mon, 21 Sep 2015 12:08:42 -0700
Eric Nelson <eric@nelint.com> escreveu:

> Add timeout support to the gpio-ir-recv driver as discussed
> in this original patch:
> 
> 	https://patchwork.ozlabs.org/patch/516827/
> 
> V2 uses the timeout field of the rcdev instead of a device tree 
> field to set the timeout value as suggested by Sean Young.
> 
> Eric Nelson (2):
>   rc-core: define a default timeout for drivers
>   rc: gpio-ir-recv: add timeout on idle

I'm ok on having a default timeout for drivers, but the better would
be to implement it at the RC core, and not inside each driver.

Regards,
Mauro

  parent reply	other threads:[~2015-10-03 14:27 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
     [not found] ` <1441980024-1944-1-git-send-email-eric-SeqgQ6RdavfQT0dZR+AlfA@public.gmane.org>
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
     [not found]     ` <1442862524-3694-2-git-send-email-eric-SeqgQ6RdavfQT0dZR+AlfA@public.gmane.org>
2015-10-03 14:25       ` Mauro Carvalho Chehab
     [not found]         ` <20151003112510.54fe2a25-+RedX5hVuTR+urZeOPWqwQ@public.gmane.org>
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
     [not found]         ` <5602AE95.9000505-SeqgQ6RdavfQT0dZR+AlfA@public.gmane.org>
2015-09-23 14:07           ` [PATCH V3 " Eric Nelson
     [not found]             ` <1443017228-16499-1-git-send-email-eric-SeqgQ6RdavfQT0dZR+AlfA@public.gmane.org>
2015-09-23 14:26               ` Sean Young
2015-10-03 14:27   ` Mauro Carvalho Chehab [this message]
2015-10-03 15:10     ` [PATCH V2 0/2] rc: Add timeout support to gpio-ir-recv 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=20151003112712.4f54925d@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).