From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [1/3] media: rc: drivers should produce alternate pulse and space timing events
Date: Tue, 19 Jun 2018 14:08:12 +0200 [thread overview]
Message-ID: <1529410092.28510.20.camel@baylibre.com> (raw)
In-Reply-To: <20180512105531.30482-1-sean@mess.org>
On Sat, 2018-05-12 at 11:55 +0100, Sean Young wrote:
> Report an error if this is not the case or any problem with the generated
> raw events.
Hi,
Since the inclusion of this patch, every 3 to 15 seconds, I get the following
message:
"rc rc0: two consecutive events of type space"
on the console of amlogic s400 platform (arch/arm64/boot/dts/amlogic/meson-axg-
s400.dts). I don't know much about ir protocol and surely there is something
worth investigating in the related driver, but ...
>
> Signed-off-by: Sean Young <sean@mess.org>
> ---
> drivers/media/rc/rc-ir-raw.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/media/rc/rc-ir-raw.c b/drivers/media/rc/rc-ir-raw.c
> index 2e50104ae138..49c56da9bc67 100644
> --- a/drivers/media/rc/rc-ir-raw.c
> +++ b/drivers/media/rc/rc-ir-raw.c
> @@ -22,16 +22,27 @@ static int ir_raw_event_thread(void *data)
> {
> struct ir_raw_event ev;
> struct ir_raw_handler *handler;
> - struct ir_raw_event_ctrl *raw = (struct ir_raw_event_ctrl *)data;
> + struct ir_raw_event_ctrl *raw = data;
> + struct rc_dev *dev = raw->dev;
>
> while (1) {
> mutex_lock(&ir_raw_handler_lock);
> while (kfifo_out(&raw->kfifo, &ev, 1)) {
> + if (is_timing_event(ev)) {
> + if (ev.duration == 0)
> + dev_err(&dev->dev, "nonsensical timing event of duration 0");
> + if (is_timing_event(raw->prev_ev) &&
> + !is_transition(&ev, &raw->prev_ev))
> + dev_err(&dev->dev, "two consecutive events of type %s",
> + TO_STR(ev.pulse));
> + if (raw->prev_ev.reset && ev.pulse == 0)
> + dev_err(&dev->dev, "timing event after reset should be pulse");
> + }
... considering that we continue the processing as if nothing happened, is it
really an error ?
Could we consider something less invasive ? like dev_dbg() or dev_warn_once() ?
> list_for_each_entry(handler, &ir_raw_handler_list, list)
> - if (raw->dev->enabled_protocols &
> + if (dev->enabled_protocols &
> handler->protocols || !handler->protocols)
> - handler->decode(raw->dev, ev);
> - ir_lirc_raw_event(raw->dev, ev);
> + handler->decode(dev, ev);
> + ir_lirc_raw_event(dev, ev);
> raw->prev_ev = ev;
> }
> mutex_unlock(&ir_raw_handler_lock);
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: Sean Young <sean@mess.org>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "open list:ARM/Amlogic Meson..." <linux-amlogic@lists.infradead.org>
Subject: Re: [1/3] media: rc: drivers should produce alternate pulse and space timing events
Date: Tue, 19 Jun 2018 14:08:12 +0200 [thread overview]
Message-ID: <1529410092.28510.20.camel@baylibre.com> (raw)
In-Reply-To: <20180512105531.30482-1-sean@mess.org>
On Sat, 2018-05-12 at 11:55 +0100, Sean Young wrote:
> Report an error if this is not the case or any problem with the generated
> raw events.
Hi,
Since the inclusion of this patch, every 3 to 15 seconds, I get the following
message:
"rc rc0: two consecutive events of type space"
on the console of amlogic s400 platform (arch/arm64/boot/dts/amlogic/meson-axg-
s400.dts). I don't know much about ir protocol and surely there is something
worth investigating in the related driver, but ...
>
> Signed-off-by: Sean Young <sean@mess.org>
> ---
> drivers/media/rc/rc-ir-raw.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/media/rc/rc-ir-raw.c b/drivers/media/rc/rc-ir-raw.c
> index 2e50104ae138..49c56da9bc67 100644
> --- a/drivers/media/rc/rc-ir-raw.c
> +++ b/drivers/media/rc/rc-ir-raw.c
> @@ -22,16 +22,27 @@ static int ir_raw_event_thread(void *data)
> {
> struct ir_raw_event ev;
> struct ir_raw_handler *handler;
> - struct ir_raw_event_ctrl *raw = (struct ir_raw_event_ctrl *)data;
> + struct ir_raw_event_ctrl *raw = data;
> + struct rc_dev *dev = raw->dev;
>
> while (1) {
> mutex_lock(&ir_raw_handler_lock);
> while (kfifo_out(&raw->kfifo, &ev, 1)) {
> + if (is_timing_event(ev)) {
> + if (ev.duration == 0)
> + dev_err(&dev->dev, "nonsensical timing event of duration 0");
> + if (is_timing_event(raw->prev_ev) &&
> + !is_transition(&ev, &raw->prev_ev))
> + dev_err(&dev->dev, "two consecutive events of type %s",
> + TO_STR(ev.pulse));
> + if (raw->prev_ev.reset && ev.pulse == 0)
> + dev_err(&dev->dev, "timing event after reset should be pulse");
> + }
... considering that we continue the processing as if nothing happened, is it
really an error ?
Could we consider something less invasive ? like dev_dbg() or dev_warn_once() ?
> list_for_each_entry(handler, &ir_raw_handler_list, list)
> - if (raw->dev->enabled_protocols &
> + if (dev->enabled_protocols &
> handler->protocols || !handler->protocols)
> - handler->decode(raw->dev, ev);
> - ir_lirc_raw_event(raw->dev, ev);
> + handler->decode(dev, ev);
> + ir_lirc_raw_event(dev, ev);
> raw->prev_ev = ev;
> }
> mutex_unlock(&ir_raw_handler_lock);
next prev parent reply other threads:[~2018-06-19 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 10:55 [PATCH 1/3] media: rc: drivers should produce alternate pulse and space timing events Sean Young
2018-05-12 10:55 ` [PATCH 2/3] media: rc: decoders do not need to check for transitions Sean Young
2018-05-12 10:55 ` [PATCH 3/3] media: rc: winbond: do not send reset and timeout raw events on startup Sean Young
2018-06-19 12:08 ` Jerome Brunet [this message]
2018-06-19 12:08 ` [1/3] media: rc: drivers should produce alternate pulse and space timing events Jerome Brunet
2018-06-19 12:57 ` Sean Young
2018-06-19 12:57 ` Sean Young
2018-06-19 14:09 ` Jerome Brunet
2018-06-19 14:09 ` Jerome Brunet
2018-06-26 14:37 ` Sean Young
2018-06-26 14:37 ` Sean Young
2018-06-26 14:39 ` Jerome Brunet
2018-06-26 14:39 ` Jerome Brunet
2018-06-26 16:33 ` Sean Young
2018-06-26 16:33 ` Sean Young
2018-06-26 16:46 ` Jerome Brunet
2018-06-26 16:46 ` Jerome Brunet
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=1529410092.28510.20.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.