From: Michael Klein <michael@fossekall.de>
To: linux-media@vger.kernel.org
Subject: [PATCH v2 0/2] media: rc: gpio-ir-recv: add timeout property
Date: Thu, 5 Nov 2020 16:35:03 +0100 [thread overview]
Message-ID: <cover.1604589023.git.michael@fossekall.de> (raw)
The default recorder timeout of 125ms is too high for some BPF protocol
decoders when a remote sends repeat codes at high rates. This makes the
timeout configurable via the devicetree.
Changes in v2:
fix checkpatch.pl warnings
Michael Klein (2):
media: rc: gpio-ir-recv: add recorder timeout property
media: bindings: media: gpio-ir-receiver: add linux,timeout-us
property
.../devicetree/bindings/media/gpio-ir-receiver.txt | 3 +++
Documentation/devicetree/bindings/media/rc.yaml | 6 ++++++
drivers/media/rc/gpio-ir-recv.c | 3 ++-
3 files changed, 11 insertions(+), 1 deletion(-)
--
2.28.0
WARNING: multiple messages have this Message-ID (diff)
From: Michael Klein <michael@fossekall.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org, Michael Klein <michael@fossekall.de>
Subject: [PATCH RESEND v2 0/2] media: rc: gpio-ir-recv: add timeout property
Date: Mon, 9 Nov 2020 16:23:09 +0100 [thread overview]
Message-ID: <cover.1604589023.git.michael@fossekall.de> (raw)
Message-ID: <20201109152309.jBT24xaP_A1n6OfxDD30s0yjfVRizGDPRg-pyzTGmLE@z> (raw)
The default recorder timeout of 125ms is too high for some BPF protocol
decoders when a remote sends repeat codes at high rates. This makes the
timeout configurable via the devicetree.
Changes in v2:
fix checkpatch.pl warnings
Michael Klein (2):
media: rc: gpio-ir-recv: add recorder timeout property
media: bindings: media: gpio-ir-receiver: add linux,timeout-us
property
.../devicetree/bindings/media/gpio-ir-receiver.txt | 3 +++
Documentation/devicetree/bindings/media/rc.yaml | 6 ++++++
drivers/media/rc/gpio-ir-recv.c | 3 ++-
3 files changed, 11 insertions(+), 1 deletion(-)
--
2.28.0
next reply other threads:[~2020-11-05 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 15:35 Michael Klein [this message]
2020-11-05 15:35 ` [PATCH v2 1/2] media: rc: gpio-ir-recv: add recorder timeout property Michael Klein
2020-11-09 15:23 ` [PATCH RESEND " Michael Klein
2020-11-05 15:35 ` [PATCH v2 2/2] media: bindings: media: gpio-ir-receiver: add linux,timeout-us property Michael Klein
2020-11-09 15:23 ` [PATCH RESEND " Michael Klein
2020-11-09 15:23 ` [PATCH RESEND v2 0/2] media: rc: gpio-ir-recv: add timeout property Michael Klein
2020-11-10 10:17 ` Sean Young
2020-11-10 12:48 ` Michael Klein
2020-11-10 13:19 ` Sean Young
2020-11-10 20:34 ` Michael Klein
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=cover.1604589023.git.michael@fossekall.de \
--to=michael@fossekall.de \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).