Skip to content

lirc_rpi: Lower IR reception error to debug #1361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 23, 2016
Merged

lirc_rpi: Lower IR reception error to debug #1361

merged 1 commit into from
Mar 23, 2016

Conversation

rfrht
Copy link
Contributor

@rfrht rfrht commented Mar 22, 2016

Sometimes the IR receiver does not understands a IR pulse and will throw lots of printks:

Mar 21 21:47:02 pi-quarto kernel: [190313.352993] lirc_rpi: AIEEEE: 1 1 56f06bd6 56f06b53 3d963 2e722
Mar 21 21:49:27 pi-quarto kernel: [190458.485894] lirc_rpi: AIEEEE: 0 0 56f06c67 56f06c39 5e08a 67f04
Mar 21 22:20:57 pi-quarto kernel: [192348.232130] lirc_rpi: AIEEEE: 1 1 56f073c9 56f07389 20147 bbca1
Mar 21 22:22:30 pi-quarto kernel: [192441.471321] lirc_rpi: AIEEEE: 0 0 56f07426 56f073ec 5a79e cb6f4
Mar 21 22:30:52 pi-quarto kernel: [192943.810652] lirc_rpi: AIEEEE: 1 1 56f0761c 56f075f4 ad520 231c0
Mar 21 22:35:14 pi-quarto kernel: [193205.705152] lirc_rpi: AIEEEE: 0 0 56f07722 56f07709 93904 ce464
Mar 22 08:42:38 pi-quarto kernel: [229649.228031] lirc_rpi: AIEEEE: 1 1 56f1057e 56f104cb 1f144 70e72
Mar 22 08:43:02 pi-quarto kernel: [229673.395809] lirc_rpi: AIEEEE: 0 0 56f10596 56f1057e 480a7 1f666

This will cause a disk/SD card wake up and a write of the printk() in /var/log/{messages,syslog,kern.log}

This commit lowers a IR reception error condition message to KERNEL_DEBUG.

Lowers a IR reception error condition message to KERNEL_DEBUG
@pelwell pelwell merged commit 43df7c1 into raspberrypi:rpi-4.1.y Mar 23, 2016
popcornmix added a commit to raspberrypi/firmware that referenced this pull request Mar 23, 2016
See: raspberrypi/linux#1361

kernel: vchiq_arm: Access the dequeue_pending flag locked
See: raspberrypi/linux@a7419d5

kernel: BCM270X_DT: Add pi3-act-led overlay
See: raspberrypi/linux#1363

firmware: sdram: cache the last set_frequency
firmware: pwm_sdm: Set SDRAM turbo frequency to default if pwm_sdm is enabled
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=136445

firmware: vchiq_lib: Don't overwrite loop count mid-loop
See: https://discourse.osmc.tv/t/frequent-random-muting-then-freezing/9875/104

firmware: arm_loader: Change mini-UART initialisation order
See: #553
popcornmix added a commit to Hexxeh/rpi-firmware that referenced this pull request Mar 23, 2016
See: raspberrypi/linux#1361

kernel: vchiq_arm: Access the dequeue_pending flag locked
See: raspberrypi/linux@a7419d5

kernel: BCM270X_DT: Add pi3-act-led overlay
See: raspberrypi/linux#1363

firmware: sdram: cache the last set_frequency
firmware: pwm_sdm: Set SDRAM turbo frequency to default if pwm_sdm is enabled
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=136445

firmware: vchiq_lib: Don't overwrite loop count mid-loop
See: https://discourse.osmc.tv/t/frequent-random-muting-then-freezing/9875/104

firmware: arm_loader: Change mini-UART initialisation order
See: raspberrypi/firmware#553
swarren added a commit to swarren/u-boot that referenced this pull request Mar 24, 2016
This allows U-Boot to known the name of the board.

The existing rpi_2_defconfig should be able to operate correctly on the
Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use
the PL011 UART as the console UART (the default is the mini UART). This
should be possible by loading the pi3-miniuart-bt DT overlay. As of
20160323 (or firmware.git commit 7f536a27cc74 "kernel: lirc_rpi: Lower IR
reception error to debug See: raspberrypi/linux#1361"
this doesn't seem to work; I assume this is due to a firmware bug.

Signed-off-by: Stephen Warren <[email protected]>
swarren added a commit to swarren/u-boot that referenced this pull request Mar 24, 2016
The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
or 64-bit mode. 32-bit mode is the current default selected by the
VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
U-Boot for the Raspberry Pi 3.

From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
UART to connect to the SoC. By default, the PL011 is used for this purpose
since it has larger FIFOs than the other ("mini" UART). However, this can
be configured via the VideoCore firmware's config.txt file. This patch
hard-codes use of the mini UART in the RPi 3 port. If your system uses the
PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
port instead. A future change might determine which UART to use at
run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
together.

The mini UART has some limitations. One externally visible issue in the
BCM2837 integration is that the UART divides the SoC's "core clock" to
generate the baud rate. The core clock is typically variable, and under
control of the VideoCore firmware for thermal management reasons. If the
VC FW does modify the core clock rate, UART communication will be
corrupted since the baud rate will vary from the expected value. This was
not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
work around this, the VideoCore firmware can be told not to modify the SoC
core clock. However, the only way this can happen and be thermally safe is
to limit the core clock to a low/minimum frequency. This leaves
performance on the table for use-cases that don't care about a UART
console. Consequently, use of the mini UART console must be explicitly
requested by entering the following line into config.txt

    enable_uart=1

A recent version of the VC firmware is required to ensure that the mini
UART is fully and correctly initialized by the VC FW. At least
firmware.git commit 7f536a27cc74 "kernel: lirc_rpi: Lower IR reception
error to debug See: raspberrypi/linux#1361" is
required. However, note that there is a bug in that version that prevents
MMC from operating correctly on any Pi. As of 20160323 that is not fixed.

Signed-off-by: Stephen Warren <[email protected]>
XECDesign pushed a commit to RPi-Distro/firmware that referenced this pull request May 4, 2016
See: raspberrypi/linux#1361

kernel: vchiq_arm: Access the dequeue_pending flag locked
See: raspberrypi/linux@a7419d5

kernel: BCM270X_DT: Add pi3-act-led overlay
See: raspberrypi/linux#1363

firmware: sdram: cache the last set_frequency
firmware: pwm_sdm: Set SDRAM turbo frequency to default if pwm_sdm is enabled
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=136445

firmware: vchiq_lib: Don't overwrite loop count mid-loop
See: https://discourse.osmc.tv/t/frequent-random-muting-then-freezing/9875/104

firmware: arm_loader: Change mini-UART initialisation order
See: raspberrypi#553
neuschaefer pushed a commit to neuschaefer/raspi-binary-firmware that referenced this pull request Feb 27, 2017
See: raspberrypi/linux#1361

kernel: vchiq_arm: Access the dequeue_pending flag locked
See: raspberrypi/linux@a7419d5

kernel: BCM270X_DT: Add pi3-act-led overlay
See: raspberrypi/linux#1363

firmware: sdram: cache the last set_frequency
firmware: pwm_sdm: Set SDRAM turbo frequency to default if pwm_sdm is enabled
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=136445

firmware: vchiq_lib: Don't overwrite loop count mid-loop
See: https://discourse.osmc.tv/t/frequent-random-muting-then-freezing/9875/104

firmware: arm_loader: Change mini-UART initialisation order
See: raspberrypi#553
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants