On Mon, Mar 12, 2018 at 09:48:40PM +0000, Sean Young wrote:
> A timeout of 200ms is much longer than necessary, and delays the decoding
> decoding of a single scancode and the last scancode when a button is being
> held. This makes the remote seem sluggish.
> 
> If the min_timeout and max_timeout values are set, the timeout is
> configurable via the LIRC_SET_REC_TIMEOUT ioctl.
> 
> Signed-off-by: Sean Young <s...@mess.org>

Tested-by: Matthias Reichl <h...@horus.com>

Thanks a lot, this is working fine!

so long,

Hias

> ---
>  drivers/media/rc/meson-ir.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/rc/meson-ir.c b/drivers/media/rc/meson-ir.c
> index 64b0aa4f4db7..f449b35d25e7 100644
> --- a/drivers/media/rc/meson-ir.c
> +++ b/drivers/media/rc/meson-ir.c
> @@ -144,7 +144,9 @@ static int meson_ir_probe(struct platform_device *pdev)
>       ir->rc->map_name = map_name ? map_name : RC_MAP_EMPTY;
>       ir->rc->allowed_protocols = RC_PROTO_BIT_ALL_IR_DECODER;
>       ir->rc->rx_resolution = US_TO_NS(MESON_TRATE);
> -     ir->rc->timeout = MS_TO_NS(200);
> +     ir->rc->min_timeout = 1;
> +     ir->rc->timeout = IR_DEFAULT_TIMEOUT;
> +     ir->rc->max_timeout = 10 * IR_DEFAULT_TIMEOUT;
>       ir->rc->driver_name = DRIVER_NAME;
>  
>       spin_lock_init(&ir->lock);
> -- 
> 2.14.3
> 

Reply via email to