Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1251561imm; Wed, 23 May 2018 12:50:39 -0700 (PDT) X-Google-Smtp-Source: AB8JxZq0wr+7zoIXKje/rTOlm2G8HgzAFVlZBPmU7pHYNPIePS47nz9Z3qHgBKe1xCZnY1wZg1ir X-Received: by 2002:a17:902:d882:: with SMTP id b2-v6mr4100483plz.220.1527105039667; Wed, 23 May 2018 12:50:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527105039; cv=none; d=google.com; s=arc-20160816; b=xy3W/ZI2sTjUoApBJjmT6p2w939Rjw5IQT8KBB3SrO4CxLnwjrs+DDmg7qPsIWBILC bu5M7r/tWEEjuyz4cf6gwG102YmGDTQ8OpdTueHrimGJuOITheA3/TEzkDfCkMmS1tOi v8GTPP15sCZcpNAgujzdEnrM5o6X6pg44rTCGSFib8FWUbnIVgS8m765BqZMnPbsD4Cj msXhg5bAQla1KeqVvuEExWOyB31uGyTm/ao1kvu0upufPxkyt016D1v1Bo6v63JKjws5 o1GcM9etEH/Ykd4coN6NticlAa5dSO+zLhzUjaveUAcxdfLgvqMCpsG50Ht8YRC/FAOA jIeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=yVx2rTZFk5MwVeLo28JMYuOt6MNeisBdpcuDtqCWNy4=; b=bU03kdmwva2rrkD+6QfyXSeD7tEMdlQA2vk2q6hWOjdnZiCUUrHXDjCzV0Uv/pfy+L GzxRWeCPXeSlRh/BrySpB/jHsM4yQyileJajzSXuRjkF9efDsJw0+QR6F5DQDaoyxLBj SFk6IbOYZfjqWcmOuEMsVlveDMGNo05XeOXF6CQPKBbna5MYZ0Agwp0dbwaZ3guVmcJk auOOMuyLi4I7s9M/eQ5rt3qaGoG3JGvT8fg+SI3lP8/E/jO241CURccZX6yjXfKGwtgv g3cREBGuvHp2EXzGNphEiMVx6yoPPjB+jC9yPR8dKn/YuDGUU+0L/5DBiR68wneBMaRJ eQlw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u11-v6si15043633pgp.480.2018.05.23.12.50.24; Wed, 23 May 2018 12:50:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934745AbeEWTuK (ORCPT + 99 others); Wed, 23 May 2018 15:50:10 -0400 Received: from gofer.mess.org ([88.97.38.141]:58709 "EHLO gofer.mess.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934181AbeEWTuI (ORCPT ); Wed, 23 May 2018 15:50:08 -0400 Received: by gofer.mess.org (Postfix, from userid 1000) id A00CF6030B; Wed, 23 May 2018 20:50:05 +0100 (BST) Date: Wed, 23 May 2018 20:50:05 +0100 From: Sean Young To: Daniel Borkmann Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, Alexei Starovoitov , Mauro Carvalho Chehab , netdev@vger.kernel.org, Matthias Reichl , Devin Heitmueller , Y Song , Quentin Monnet Subject: Re: [PATCH v4 0/3] IR decoding using BPF Message-ID: <20180523195005.nltyuyfmwko4ate2@gofer.mess.org> References: <860cf2a8-dd2e-ba78-8b98-3d8f4330f3d0@iogearbox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <860cf2a8-dd2e-ba78-8b98-3d8f4330f3d0@iogearbox.net> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 23, 2018 at 02:21:27PM +0200, Daniel Borkmann wrote: > On 05/18/2018 04:07 PM, Sean Young wrote: > > The kernel IR decoders (drivers/media/rc/ir-*-decoder.c) support the most > > widely used IR protocols, but there are many protocols which are not > > supported[1]. For example, the lirc-remotes[2] repo has over 2700 remotes, > > many of which are not supported by rc-core. There is a "long tail" of > > unsupported IR protocols, for which lircd is need to decode the IR . > > > > IR encoding is done in such a way that some simple circuit can decode it; > > therefore, bpf is ideal. > > > > In order to support all these protocols, here we have bpf based IR decoding. > > The idea is that user-space can define a decoder in bpf, attach it to > > the rc device through the lirc chardev. > > > > Separate work is underway to extend ir-keytable to have an extensive library > > of bpf-based decoders, and a much expanded library of rc keymaps. > > > > Another future application would be to compile IRP[3] to a IR BPF program, and > > so support virtually every remote without having to write a decoder for each. > > It might also be possible to support non-button devices such as analog > > directional pads or air conditioning remote controls and decode the target > > temperature in bpf, and pass that to an input device. > > Mauro, are you fine with this series going via bpf-next? How ugly would this > get with regards to merge conflicts wrt drivers/media/rc/? There are no merge conflict and as of yet, I'm not expecting any. If anything I suspect the bpf tree is more likely to change, so merging via bpf-next might make more sense. Thanks Sean > > Thanks, > Daniel > > > Thanks, > > > > Sean Young > > > > [1] http://www.hifi-remote.com/wiki/index.php?title=DecodeIR > > [2] https://sourceforge.net/p/lirc-remotes/code/ci/master/tree/remotes/ > > [3] http://www.hifi-remote.com/wiki/index.php?title=IRP_Notation > > > > Changes since v3: > > - Implemented review comments from Quentin Monnet and Y Song (thanks!) > > - More helpful and better formatted bpf helper documentation > > - Changed back to bpf_prog_array rather than open-coded implementation > > - scancodes can be 64 bit > > - bpf gets passed values in microseconds, not nanoseconds. > > microseconds is more than than enough (IR receivers support carriers upto > > 70kHz, at which point a single period is already 14 microseconds). Also, > > this makes it much more consistent with lirc mode2. > > - Since it looks much more like lirc mode2, rename the program type to > > BPF_PROG_TYPE_LIRC_MODE2. > > - Rebased on bpf-next > > > > Changes since v2: > > - Fixed locking issues > > - Improved self-test to cover more cases > > - Rebased on bpf-next again > > > > Changes since v1: > > - Code review comments from Y Song and > > Randy Dunlap > > - Re-wrote sample bpf to be selftest > > - Renamed RAWIR_DECODER -> RAWIR_EVENT (Kconfig, context, bpf prog type) > > - Rebase on bpf-next > > - Introduced bpf_rawir_event context structure with simpler access checking > > > > Sean Young (3): > > bpf: bpf_prog_array_copy() should return -ENOENT if exclude_prog not > > found > > media: rc: introduce BPF_PROG_LIRC_MODE2 > > bpf: add selftest for lirc_mode2 type program > > > > drivers/media/rc/Kconfig | 13 + > > drivers/media/rc/Makefile | 1 + > > drivers/media/rc/bpf-lirc.c | 308 ++++++++++++++++++ > > drivers/media/rc/lirc_dev.c | 30 ++ > > drivers/media/rc/rc-core-priv.h | 22 ++ > > drivers/media/rc/rc-ir-raw.c | 12 +- > > include/linux/bpf_rcdev.h | 30 ++ > > include/linux/bpf_types.h | 3 + > > include/uapi/linux/bpf.h | 53 ++- > > kernel/bpf/core.c | 11 +- > > kernel/bpf/syscall.c | 7 + > > kernel/trace/bpf_trace.c | 2 + > > tools/bpf/bpftool/prog.c | 1 + > > tools/include/uapi/linux/bpf.h | 53 ++- > > tools/include/uapi/linux/lirc.h | 217 ++++++++++++ > > tools/lib/bpf/libbpf.c | 1 + > > tools/testing/selftests/bpf/Makefile | 8 +- > > tools/testing/selftests/bpf/bpf_helpers.h | 6 + > > .../testing/selftests/bpf/test_lirc_mode2.sh | 28 ++ > > .../selftests/bpf/test_lirc_mode2_kern.c | 23 ++ > > .../selftests/bpf/test_lirc_mode2_user.c | 154 +++++++++ > > 21 files changed, 974 insertions(+), 9 deletions(-) > > create mode 100644 drivers/media/rc/bpf-lirc.c > > create mode 100644 include/linux/bpf_rcdev.h > > create mode 100644 tools/include/uapi/linux/lirc.h > > create mode 100755 tools/testing/selftests/bpf/test_lirc_mode2.sh > > create mode 100644 tools/testing/selftests/bpf/test_lirc_mode2_kern.c > > create mode 100644 tools/testing/selftests/bpf/test_lirc_mode2_user.c > >