IR receiver: decode untested with a real remote #16
Labels
No labels
blocked-physical
cleanup
hardware
infra
kernel
P1-critical
P2-high
P3-normal
P4-later
reliability
security
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tiagoagueda/a80#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Resolved 2026-08-28 — see the new section at the end of
39-ir-and-leds.md.
It did not decode, and the cause was not the receiver. The remote was confirmed transmitting on
a phone camera; nine minutes of key presses produced 25 bytes of capture, pulses of 16-32 us
where a NEC leader is 9000 us.
The hardware was ruled in step by step:
pin 358 (PL6): 8002000.ir … function s_cir_rx✓vcc-pl-supply = <®_cldo1>, consumer present ✓The cause was the sample clock:
sunxi-cirwants 8 MHz and converts hardware sample counts to microseconds assuming itsclk_set_rate()succeeded. A mod0 factors clock only divides from whatever parent it alreadyhas and never reparents, so the request lands ~3900x off and nothing decodes.
Writing
0x81000002(mux=1 osc24M, M=2, so 24 MHz / 3 = 8 MHz) fixes it outright:59 NEC frames, eleven distinct scancodes, all NEC address
0x10:0x1000 0x1001 0x1005 0x1007 0x1013 0x101b 0x1041 0x1045 0x1046 0x1055 0x105d⚠️ It currently needs
probe/irclk.koloaded — the device-tree fix does not take effect. Splitout as its own issue.
⚠️ Nothing has been submitted upstream. See 42-upstreaming.md.