Re: [ISSUE] [CLOSED] LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

Re: [ISSUE] [CLOSED] LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]

Closed issue by Leon-Plickat on void-packages repository

https://github.com/void-linux/void-packages/issues/10905

Description:
I tried using a IR receiver connected to the GPIO ports of the Pi, but was unable to get the LIRC driver to work.

I followed the steps described on [this website](http://alexba.in/blog/2013/01/06/setting-up-lirc-on-the-raspberrypi/). Other website describe a similar procedure to get IR via GPIO working, so I believe this is the correct way. As basically all Pi related information on the internet, it assumes one is using Raspbian. However it should still apply to every distribution whichs kernel has the correct driver.

I tried both: Doing exactly as described in the article as well as adapting it to void (meaning things like creating `/etc/modules-load.d/lirc.conf` instead of modifying `/etc/modules`). But `/dev/lirc0` never appeared.

Appearently, the LIRC driver in the kernel needs to patched in order for it to work with GPIO, [as described on the website of the author of mentioned patch](http://aron.ws/projects/lirc_rpi/).

Since someone on Reddit (from where I was referred to here) mentioned that they got LIRC to work with an USB IR receiver on the Pi, I believe that the default LIRC drivers are in voids kernel, however as the user space tools of LIRC are not packaged in void aarch64, I am tempted to believe that the patch is also not applied to the driver.

Is my assumption, that the version of LIRC patched to work with the GPIO ports of the Pi is not included in voids aarch64 kernel, correct? Or am I missing something? And if this is the case, is there any way of getting LIRC to work with a IR receiver connected via GPIO?

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1130495144

Comment:
Can this be reopened? I'm facing the same issue. Trying to attach an IR receiver on my RPI 3 B+ but it seems like [lirc](https://www.lirc.org/) is not packaged yet? Is there a replacement that I can use for now?

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
One needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 3013 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
One needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 3865 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
One needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 4131 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys manually.

(to be continued)

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5198 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys manually.

I have a (Pine64 IR Remote)[https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/] which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5341 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys manually.

I have a (Pine64 IR Remote)[https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/] which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.conf` or similiar to automate this on boot.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5342 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys manually.

I have a (Pine64 IR Remote)[https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/] which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.local` or similiar to automate this on boot.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5344 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys "manually".

I have a [Pine64 IR Remote[(https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/) which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.local` or similiar to automate this on boot.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5344 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys "manually".

I have a [Pine64 IR Remote](https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/) which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.local` or similiar to automate this on boot.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5495 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys "manually".

I have a [Pine64 IR Remote](https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/) which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.local` or similiar to automate this on boot.

Edit:
This should suffice inside `/boot/config.txt`
```
dtoverlay=gpio-ir,gpio_pin=17,gpio_pull=1,rc-map-name=<keymap file for your remote>
```

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5513 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys "manually".

I have a [Pine64 IR Remote](https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/) which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.local` or similiar to automate this on boot.

Edit:
This should suffice inside `/boot/config.txt` (Replaces Part 3)
```
dtoverlay=gpio-ir,gpio_pin=17,gpio_pull=1,rc-map-name=<keymap file for your remote>
```

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 5344 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1131306568

Comment:
Turns out v4l is used nowadays for IR communication, the package should already be installed (`v4l-utils`).
Based on https://www.instructables.com/Setup-IR-Remote-Control-Using-LIRC-for-the-Raspber/
one needs to add the following options to /boot/config.txt:

```
dtoverlay=gpio-ir,gpio_pin=17
```

Where gpio_pin is the Pin used for communication with the IR. 

Example: https://miro.medium.com/max/1400/1*A2gpUDLyOx903dVUStHFTA.jpeg

I've connected mine to the GPIO number 17, so that's what I enabled.
Reboot, then you have /dev/lirc0 and can run `# rc-keytable` and receive:

```
# LC_ALL=C ir-keytable
Found /sys/class/rc/rc1/ with:
        Name: vc4
        Driver: cec
        Default keymap: rc-cec
        Input device: /dev/input/event1
        Supported kernel protocols: cec
        Enabled kernel protocols: cec
        bus: 30, vendor/product: 0000:0000, version: 0x0001
        Repeat delay = 0 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ with:
        Name: gpio_ir_recv
        Driver: gpio_ir_recv
        Default keymap: rc-rc6-mce
        Input device: /dev/input/event0
        LIRC device: /dev/lirc0
        Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        Enabled kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
```

Now you can test your remote via `sudo ir-keytable -c -p all -t`.

```
LC_ALL=C ir-keytable -c -p all -t
Old keytable cleared
Protocols changed to unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp cec imon rc-mm
Can't find xbox-dvd bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev/rc_keymaps/protocols
Testing events. Please, press CTRL-C to abort.
623.497051: lirc protocol(necx): scancode = 0x404008 repeat
623.497098: event type EV_MSC(0x04): scancode = 0x404008
623.497098: event type EV_SYN(0x00).
624.302063: lirc protocol(necx): scancode = 0x404010
624.302096: event type EV_MSC(0x04): scancode = 0x404010
624.302096: event type EV_SYN(0x00).
624.361055: lirc protocol(necx): scancode = 0x404010 repeat
624.361088: event type EV_MSC(0x04): scancode = 0x404010
624.361088: event type EV_SYN(0x00).
624.867071: lirc protocol(necx): scancode = 0x40400b
624.867102: event type EV_MSC(0x04): scancode = 0x40400b
624.867102: event type EV_SYN(0x00).
624.926056: lirc protocol(necx): scancode = 0x40400b repeat
624.926090: event type EV_MSC(0x04): scancode = 0x40400b
624.926090: event type EV_SYN(0x00).
625.408074: lirc protocol(necx): scancode = 0x40400e
625.408103: event type EV_MSC(0x04): scancode = 0x40400e
625.408103: event type EV_SYN(0x00).
625.467074: lirc protocol(necx): scancode = 0x40400e repeat
625.467109: event type EV_MSC(0x04): scancode = 0x40400e
625.467109: event type EV_SYN(0x00).
```

(Part 2)

`/usr/share/lirc/contrib/60-lirc.rules` contains:

```
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
```

Adding lirc group: `groupadd lirc`

Reloading udev:

```sh
# udevadm control -R
# udevadm trigger
```

Checking permissions: 
```sh
# ls -lisah /dev/lirc0
164 0 crw-rw---- 1 root lirc 251, 0 19. Mai 10:26 /dev/lirc0
```

Adding group to user: `usermod -aG lirc <USER>`

Hint: Your user also needs to be inside the `input` group to use /dev/input/* devices (`usermod -aG input <USER>`).

(Logging out & in)
Checking groups:
```sh
$ groups
... lirc
```

Check features with normal user:
```
$ LC_ALL=C ir-ctl --features
Receive features /dev/lirc0:
 - Device can receive raw IR
 - Can report decoded scancodes and protocol
 - Receiving timeout 12664 microseconds
 - Can set receiving timeout min 1 microseconds, max 1250000 microseconds
Send features /dev/lirc0:
 - Device cannot send
```

(Part 3)
As per https://mauricius.dev/configure-an-infrared-remote-control-with-linux/ 
we now need to map the events to the correct keys "manually".

I have a [Pine64 IR Remote](https://pine64.com/product/pine64-ir-remote-with-ir-receiver-sensor/) which means I should have a file `pine64.toml` inside `/lib/udev/rc_keymaps`.

By reloading the keytable with this mappings, it should now read the events correctly.

```
# ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml
```

```
$ LC_ALL=C ir-keytable -t
Testing events. Please, press CTRL-C to abort.
784.668064: lirc protocol(necx): scancode = 0x40404d
784.668107: event type EV_MSC(0x04): scancode = 0x40404d
784.668107: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)
784.668107: event type EV_SYN(0x00).
784.727063: lirc protocol(necx): scancode = 0x40404d repeat
784.727098: event type EV_MSC(0x04): scancode = 0x40404d
784.727098: event type EV_SYN(0x00).
784.856040: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)
784.856040: event type EV_SYN(0x00).
```

Success! It now prints `key_down` and `key_up` events for the remote. 
You can probably add the command `ir-keytable -c -w /lib/udev/rc_keymaps/pine64.toml` to `/etc/rc.local` or similiar to automate this on boot.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[zdykstra]

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

New comment by zdykstra on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1397730950

Comment:
I'm a bit late here, but I've started packaging `lirc` in https://github.com/zdykstra/void-packages/tree/lirc/srcpkgs/lirc . I've gone this route because the remote I want to use is unsupported by the devinput layer, so I had to create a custom profile with `irrecord`.  The package has only been tested on `x86_64`.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 377 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1398022684

Comment:
@zdykstra are you saying that even with a custom keymap your device cannot be used?
I'm curious now, what type of device are you using?

Hint for the googlers:
`/usr/lib/udev/rc_keymaps/` is the new path to the `rc_keymap`s now.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 281 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1398022684

Comment:
@zdykstra are you saying that even with a custom keymap your device cannot be used?
I'm curious now, what type of device are you using?

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[zdykstra]

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

New comment by zdykstra on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1398438046

Comment:
Much to my disappointment, that's right.  The remote doesn't speak any of the IR protocols that the devinput layer supports.

`ir-keytable -v -t -p rc-5,rc-5-sz,jvc,sony,nec,sanyo,mce_kbd,rc-6,sharp,xmp,imon,rc-mm`

I had to use LIRC to make a custom remote protocol, where it can discover the gaps between pulses, how they're terminated, etc. It's a remote for a piece of stereo equipment.

Re: LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/10905#issuecomment-1099749380

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.