Skip to content
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

HDMI screen blanking but not switching off backlight - Pi 4 #3050

Closed
notGMman opened this issue Jul 4, 2019 · 68 comments
Closed

HDMI screen blanking but not switching off backlight - Pi 4 #3050

notGMman opened this issue Jul 4, 2019 · 68 comments
Assignees

Comments

@notGMman
Copy link

notGMman commented Jul 4, 2019

Describe the bug
Issue noted on a Raspberry Pi 4, running Buster using both the stable kernel and the current bleeding edge.
The setting in /boot/config.txt "hdmi_blanking=1 is set. The X dpms settings are active. The screen blanks after the defined timeout but the backlight stays on.
This issue does not occur on a respberry pi 3b+ with the same SD card (this was tested prior to upgrading the kerne - so only on the current stable kernell)
This occurs on an ASUS HDMI monitor. Have no other display devices to test with.

To reproduce
Configure /boot/config.txt with hdmi_blanking=1.
In /etc/xdg/lxsession/LXDE-pi/autostart add:
point-rpi
@xset s 0 0
@xset s noblank
@xset s noexpose
@xset dpms 0 0 300

Expected behaviour
Screen blanks after 5 miniutes. Backlight switches off when screen receives no HDMI signal.

Actual behaviour
On Pi 3b+, after blanking the screen briefly displays blue with backlight, then switches off (which is fine). On Pi 4 it blanks completely, then the backlight switches on (which is no so good).

System
Pi 4.
Debian 10.0 Kernel4.19.50-v7l+ #895 and
Debian 10.0 Kernel 4.19.57-v7l+ #1244

Logs
Nothing logged in Xorg.0.log.

Additional context
Happy to try any suggested troubleshooting.

@timg236
Copy link
Contributor

timg236 commented Jul 5, 2019

hdmi_blanking=1 isn't implemented yet on Pi4, due to differences in the HDMI hardware. Hopefully, this can be fixed via a firmware update.

@notGMman
Copy link
Author

notGMman commented Jul 6, 2019

Thanks timg236 for the info. Are you aware of whether it's on anyone's radar for fixing?

@pelwell
Copy link
Contributor

pelwell commented Jul 6, 2019

Yes it is - Tim is one of us.

@timg236
Copy link
Contributor

timg236 commented Jul 6, 2019

Yes, it's on the radar along with hdmi_boost which also isn't implemented. It's a little way down the list behind general display stability & power management bugs (and probably PXE boot for improving test automation).
There's a new HDMI block and HDMI PHY so this is more of a re-implement rather than a trivial port. Possible but needs a little though to avoid problems where the display doesn't come back or causes a lockup.

@notGMman
Copy link
Author

notGMman commented Jul 7, 2019

Thanks for the updates Tim & Phil. I think I can cope with turning the screen off for the time being :-)
The irony for me is that I look after Pi's running signage at work and where they use TVs as displays (which they do because budgetholders buy whatever TV is on offer) I've had real trouble sometimes stopping them from switching off. And now at home I have the opposite problem!
Still love Pi's though.

@mehrvarz
Copy link

Hi, I have what appears to be the same issue. Not on Pi4, but on Buster.
Some time after booting, the screen blanks. I can then still ssh into the box and even make cvlc play back videos. But the gui is gone. All is pitch black. In my case, the issue seems to be related to drm_crtc_vblank_get() not returning 0 and the vc4 driver crashing, here:
https://github.com/raspberrypi/linux/blob/rpi-4.19.y/drivers/gpu/drm/vc4/vc4_firmware_kms.c#L899
notGMman, did you check dmesg? Please let me know if you see the same "Xorg Tainted" stack trace. If not, I should file a separate issue.
Here some other people having the same issue:
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=244796

@mehrvarz
Copy link

A person just posted a fix for the screen blanking issue. Maybe not a complete solution, but an effective fix:
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=244796#p1504694

@mehrvarz
Copy link

notGMman, I hope you don't mind if I litter your thread a little more, but today I apt-upgraded the kernel from 4.19.57-v7+ to 4.19.58-v7+ and the blanking fix, mentioned above, has stopped working. I had a great 48h with no screen blanking issues, but the new kernel now gives me this choice: a) use an unmodified /etc/lightdm/lightdm.conf and have the screen blank on me 10-20 minutes after boot, or b) modify /etc/lightdm/lightdm.conf with what has worked with 4.19.57-v7+ ("xserver-command=X -s 0 dpms") and have the screen blank on me when x11 is starting up. I'm picking a) for the time being...
ssh and everything else still working fine.

@6by9
Copy link
Contributor

6by9 commented Jul 23, 2019

#3020 The vblank warnings (not crash) are harmless.

@mehrvarz
Copy link

The warnings are gone with 4.19.58-v7+. But the x11-blanking is back.

Q: How is it possible that "xserver-command=X -s 0 dpms" did totally fix the issue in 4.19.57-v7+, but under 4.19.58-v7+ doing the same leads to the immediate blanking of x11?

@mehrvarz
Copy link

The warnings are still here also. My dmesg log: https://pastebin.com/raw/J2Zsbbr2

The first two warnings don't have a blanking effect. But the third warning (at time stamp 765.364852) correlates exactly with the full blanking of the x11 session.

I say "blanking of the x11 session" and not "HDMI screen blanking" like OP did, because I am able to use cvlc and/or omxplayer (via ssh) to play back videos on screen AFTER the blanking has occured. Apparently, there is nothing wrong with the HDMI signal. It's just that the screen is all black and I assume it has something to do with x11.

Also note that this is not at all Pi4 specific.

@6by9
Copy link
Contributor

6by9 commented Jul 24, 2019

The warnings will be present if you have dtoverlay=vc4-fkms-v3d in config.txt, and are noted under #3020 (as I have already linked to).
They are harmless and are due to producing DRM flip events at incorrect moments around mode changes. They have no actual link to screen blanking itself.

As timg236 has already said, HDMI display blanking is still on the radar as a feature to be implemented. Currently the screensaver will remove all layers from the screen, but the pipeline will continue to produce black output.

@mehrvarz
Copy link

If the kernel warnings are unrelated, then I apologize. The warnings state "Xorg Tainted", which fits just too well with the situation.

Currently the screensaver will remove all layers from the screen, but the pipeline will continue to produce black output.

Can I prevent the screensaver from doing that, maybe disable it before hand? Or do something after the fact, maybe by restarting a service? I am currently rebooting the device about every 10 minutes.

@6by9
Copy link
Contributor

6by9 commented Jul 24, 2019

@mehrvarz You've hijacked someone else's report of screen blanking not putting the monitor into standby mode with something different. Please don't do that.

All the X screensaver settings can be tweaked via xset s <command> (read status with xset q). You probably want xset s off if you're not wanting the screensaver to ever kick in, and xset -dpms to stop the monitor sleeping (or at least attempting to sleep).
(xset by itself gives you the help text)

@mehrvarz
Copy link

@mehrvarz You've hijacked someone else's report of screen blanking not putting the monitor into standby mode with something different. Please don't do that.

All the X screensaver settings can be tweaked via xset s <command> (read status with xset q). You probably want xset s off if you're not wanting the screensaver to ever kick in, and xset -dpms to stop the monitor sleeping (or at least attempting to sleep).
(xset by itself gives you the help text)

I am not sure my issue is different. Up to this minute I was convinced that it is the same issue. If those are different, then they certainly look the same.

I am using these xset commands in my /etc/xdg/lxsession/LXDE-pi/autostart since forever like so:
@xset s noblank
@xset s off
@xset -dpms

@6by9
Copy link
Contributor

6by9 commented Jul 24, 2019

Original report:

Expected behaviour
Screen blanks after 5 miniutes. Backlight switches off when screen receives no HDMI signal.

Actual behaviour
On Pi 3b+, after blanking the screen briefly displays blue with backlight, then switches off (which is fine). > On Pi 4 it blanks completely, then the backlight switches on (which is no so good).

ie the issue is that it isn't turning off the backlight / making the monitor sleep.

Your issue appears to be that the screen blanks in the first place, which is a very different issue.

I've checked xset s off xset -dpms, and my monitor hasn't blanked in the last hour. I see nothing further to do on that.

@notGMman
Copy link
Author

Hi 6by9
I may be about to litter my own report. I do agree that that @mehrvarz issue is not the one I reported. However, I do also see a very similar issue to his. With the dpms settings above (because blanking the screen is better than nothing!), my screen goes black for several seconds during use. it happens intermittently whilst I'm typing and coincides with a kernel "xorg.tainted" error that does appear to be the same as reported above.
Is this a known issue? I've not found anyone reporting it on the raspberry pi forum, aside from me!
Regards

@6by9
Copy link
Contributor

6by9 commented Jul 25, 2019

AIUI DPMS blanking is meant to be triggered by disabling the CRTC from DRM/KMS. That action is missing.

However the FKMS driver does support changing HDMI modes, and as part of that we issue avmute and various other commands over the HDMI link as required by the HDMI spec (I believe). Waking up from sleep normally includes a mode reset for various reasons, so it is most likely the avmute then that is being interpreted by your monitor as a sleep/backlight off request.
Why it is happening whilst you are typing is a totally different question, and one I can't answer at present.

@crocy
Copy link

crocy commented Aug 2, 2019

Any info when this would be fixed? I have the same issue even though I'm not even using a HDMI interface. I have an official RPi 7" screen connected to my Pi 4B via a display cable and also can't turn off the screen with dpms force off (it just blanks).

I can turn it on/off with echo 0 > /sys/class/backlight/rpi_backlight/bl_power but I want it to turn off automatically after a certain timeout and come back on on user press/interaction.

@6by9
Copy link
Contributor

6by9 commented Aug 2, 2019

@crocy You're bringing in a totally separate issue. This issue is for DPMS blanking of HDMI displays only.

The 7" display is a DSI display and I don't believe it has ever supported blanking via the screensaver/DPMS calls.
DSI and DPI displays control their backlights in a totally different manner to HDMI, therefore this is a different issue, and different solution required. It can be added to the list of tasks, but isn't a high priority.

@crocy
Copy link

crocy commented Aug 2, 2019

Hey, thanks for the info. The issue seemed the same to me (that's why I commented on this thread, not a new one), because I had no issues with blanking/turning off on an older Pi 3B (same interface, same display) using the same command.
I can open a new issue if you think that would be more appropriate?

@6by9
Copy link
Contributor

6by9 commented Aug 2, 2019

I had no issues with blanking/turning off on an older Pi 3B (same interface, same display) using the same command.

Trying this on a Pi3 with DSI display and I can't tell if the backlight goes off or not, and I haven't got a current meter to hand to measure that.
/sys/class/backlight/rpi_backlight/bl_power is still reporting it as on, but that may well be a quirk of the driver thinking it is the absolute master when it isn't.

Please open a new issue to allow us to track this better.

@crocy
Copy link

crocy commented Aug 2, 2019

Will do. Can you just advise me if I should post it under "linux" or "firmware" repo?

Hm, or the #1210 firmare issue could just be reopened?

@frankgould
Copy link

frankgould commented Aug 12, 2019

I am experiencing the same issue with a Spectre E16 HDMI monitor on RPi4B/4GB. Using dpms, it does not turn the monitor off, it just blanks the screen on timeout. When I hit a key or mouse moved, the monitor turns off then back on with the OSD saying HDMI connected.

@nor500
Copy link

nor500 commented Oct 3, 2019

What is the timeframe do you think the firmware can be corrected to make pi4 can send the hdmi display to go in a low power standby mode? Or is it a hadware limitation of the pi 4 hardware which will never be able to activate a proper hdmi display standby?

@JamesH65
Copy link
Contributor

JamesH65 commented Oct 3, 2019

I don't believe this a HW limitation, so it's hopefully just a matter of finding some time to implement it

@Kealper
Copy link

Kealper commented Nov 3, 2019

@nor500 It's available now if you use rpi-update, it works flawlessly on my setup, definitely a huge thanks to @JamesH65 for getting this fixed up.

@frankgould
Copy link

Ditto: "huge thanks to @JamesH65 " for making this happen!!! Works great, even on Arch Linux ARM. My desktop is now complete!

@JamesH65
Copy link
Contributor

JamesH65 commented Nov 3, 2019

Cool, its made it to rpi-update. Can people using it keep an eye on it, and report back any issues please. Not expecting any, but this is one of those changes that might have some unintended consequences.

@nor500
Copy link

nor500 commented Nov 3, 2019

Hello everyone. I am testing this latest update. However, It is not working as it supposed to be. Standby mode is turning off the hdmi port instead of putting the screen to standby mode. My settings is: DPMS (Energy Star):
Standby: 60 Suspend: 65535 Off: 65535
DPMS is Enabled

@HankB
Copy link

HankB commented Nov 5, 2019 via email

@JamesH65
Copy link
Contributor

JamesH65 commented Nov 5, 2019

I don't believe it has got to the repo's yet - we like to leave time for testing to shake out bugs for all the changes that have been made, not just this one. Not sure when the next release is, just spoken to the people involved, need to check there isn't anything that might cause problems but could be out in next day or two.

@asdf1nit
Copy link

asdf1nit commented Nov 9, 2019

Confirmed this works for me. Just used rpi-update and this fixed the backlight issue. I have an energy star monitor with dpms on

@JamesH65
Copy link
Contributor

JamesH65 commented Nov 9, 2019

Hello everyone. I am testing this latest update. However, It is not working as it supposed to be. Standby mode is turning off the hdmi port instead of putting the screen to standby mode. My settings is: DPMS (Energy Star):
Standby: 60 Suspend: 65535 Off: 65535
DPMS is Enabled

Yes, this is working as written. I simply turn off the HDMI, which in all the devices I have tried, also turns off the monitor. Sending a CEC command or whatever is required to turn off is unlikely to be done, just don't have the time given this method works for most people.

@gdevacc12
Copy link

DPMS is working fine on Raspbian (Pi4B). Thanks for the fixes.

I am not sure if there's much overlap between Raspberry Pi Foundation and Canonical with kernel builds, or indeed resolution of other issues, please clarify if possible. My apologies if below is not relevant to this issue, but just in case it's of interest:

DPMS is still a problem for Xubuntu on Ubuntu 19.10 ARM64.

xset dpms force off blanks the screen but leave the back light on
tvservice -o does switch off hdmi

I'm not sure if this is a kernel or xubuntu issue as tvservice works but I've posted the issue on the Ubuntu Desktop forum with optimism ;-)

@JimJamUrCode
Copy link

Yep working for me here as well

sudo rpi-update

This did the trick

@JamesH65
Copy link
Contributor

I am not sure if there's much overlap between Raspberry Pi Foundation and Canonical with kernel builds, or indeed resolution of other issues, please clarify if possible. My apologies if below is not relevant to this issue, but just in case it's of interest:

DPMS is still a problem for Xubuntu on Ubuntu 19.10 ARM64.

xset dpms force off blanks the screen but leave the back light on
tvservice -o does switch off hdmi

I'm not sure if this is a kernel or xubuntu issue as tvservice works but I've posted the issue on the Ubuntu Desktop forum with optimism ;-)

No overlaps at all, we don't have contact with Canonical, so any issues on Ubuntu should be reported to them. It's almost always them needing to pick up the latest firmware (and any other changes that work with that firmware as in this case)

@Boerni-tech
Copy link

It seems like the Issue still persists with the Legay driver (raspi-config, option 7, option A7, G1). With G2 its fixed...

@JamesH65
Copy link
Contributor

It seems like the Issue still persists with the Legay driver (raspi-config, option 7, option A7, G1). With G2 its fixed...

This change was specifically targeted at the FKMS driver which is the default on the Pi4, but IIRC I would expect some of the functionality to work in legacy. What specific command is not working?

@Boerni-tech
Copy link

Not a specifc command. It's just the screen not going to standby...

@dfunkt
Copy link

dfunkt commented Dec 21, 2019

Hello everyone. I am testing this latest update. However, It is not working as it supposed to be. Standby mode is turning off the hdmi port instead of putting the screen to standby mode. My settings is: DPMS (Energy Star):
Standby: 60 Suspend: 65535 Off: 65535
DPMS is Enabled

Yes, this is working as written. I simply turn off the HDMI, which in all the devices I have tried, also turns off the monitor. Sending a CEC command or whatever is required to turn off is unlikely to be done, just don't have the time given this method works for most people.

I also encountered this issue on my LG 23EA63V-P monitor, it keeps spitting out "No signal" for about 5 minutes until it finally decides to turn off. I suppose there's no way to disable this behaviour? (besides going back to an older firmware without this change, since on the latest stable firmware it goes directly into power-saving mode)

@JamesH65
Copy link
Contributor

@dfunkt what you are describing is intentional behaviour, which you have to specifically turn on (DPMS power I think its called in xscreensaver). So you need to turn it ON to get the HDMI block to power down, which in turn will cause most monitors to power off as well. Sounds like in your case you just need to turn off the screen saver completely.

@dfunkt
Copy link

dfunkt commented Dec 21, 2019

@JamesH65 I now realize that I may have worded my question poorly. What I meant to ask was if there was a way to make the display go into the power-saving mode instead of powering off with the latest firmware since that's what I prefer. (With the stable firmware it goes into the power-saving mode)

@JamesH65
Copy link
Contributor

JamesH65 commented Dec 22, 2019

So you want the monitor to go in to power saving but leave the HDMI port on the Pi powered up?
We have two modes of 'screensaving'. By default the screen goes blank, but the HDMI is powered up so it's just displaying a fully black image. I think some monitors after a while will realise this and turn themselves off. The second mode (DPMS its called in xscreensaver I think) will actually power down the HDMI port. Most monitors will detect this immediately and power themselves down. There is no option to tell the monitor to power down via CEC or similar but leave the HDMI on.

@audas
Copy link

audas commented Dec 26, 2019

I am really sorry about this and hope it comes across without sounding like a rant, appologies for any offence or poor wording.

There has been so much confusion regarding screen blanking and powering down, especially between the various pi versions. I am now very unsure of what to do.
I am on a pi 4 and am trying to control the screen turning on an off at set times - these come from a remote database.

Basically, on a pi 4 :
If I want to shut the screen down and then wake it up what should I be using.

I have tried
sudo vcgencmd display_power 0
sudo tvservice -o
sudo xset dpms force off'

Edit: just to add to wake this up I am using
`
subprocess.call('sudo xset dpms force on', shell=True)

subprocess.call('sudo tvservice -p', shell=True)

subprocess.call('sudo vcgencmd display_power 1', shell=True)  

subprocess.call('sudo xset -display :0 s noblank', shell=True)

subprocess.call('sudo xset -display :0 s off', shell=True)

subprocess.call('sudo xset -display :0 s 0 0', shell=True)

subprocess.call('sudo xset -display :0 s dpms 0 0 0', shell=True)`

However the pi will now no longer wake up and the system is totally unreachable from keyboard, mouse, SSH, putty can not even ping it. People are suggesting the wifi is powering off as well ?

Apparantly even xscreensaver over writes the display settings and can no longer be used as well - adding more confusion ?

I just want to be able to turn it on and then off then back on - so many different and totally conflicting pieces of advice.

@JamesH65
Copy link
Contributor

Those commands cannot affect Wifi.

I use xscreensaver, and it works fine, but I am using the latest rpi-update firmware - but I think the newer screen blanking code should be in apt - not sure.

So you can set up a time delay before blanking using xscreensaver, and can also use that to also turn of the HDMI output if you want.

You can also use vcgencmd display_power to turn the power on and off. There is a bug fix going through to make this one a bit more robust but the basics should work.

@frankgould
Copy link

Just to throw my "two cents" worth of experience in here, I am running Arch Linux ARM 4.19 on my RPi 4B:4GB desktop with HDMI monitor that appears to be working fine for my use. I have tested the subprocess vcgencmd commands from python3 and LXSessions and they work for me. Thought you might want to compare the OSes to see if you get different results. I use mine with dpms in LXSessions with xset s off.

@JamesH65
Copy link
Contributor

Latest official software release has all these fixes in, so closing.

@audas
Copy link

audas commented Feb 29, 2020

New software tested and working on Raspberry 4 2Gig and Raspberry 4 4Gig - but is failing on Raspberry 3 A+.

TVSERVICE causes the screen to go blank and all access to the pi is lost. Can not be retrieved without pulling power.

My script runs at start up - hence this problem completely negates my entire set up (screen blanks, can not access - I have a 60 second delay on the boot up lucky for me).

@JamesH65
Copy link
Contributor

Can you create a new issue please, this one is specifically about the Pi4. Once there something official I can try and find a 3A+ and test it out. Does seem odd it seems to kill it completely.

@SwistakGca90
Copy link

SwistakGca90 commented Apr 26, 2020

@JamesH65 i have the same issue. My raspberry Pi4 4GB turn off the hdmi after couple minutes. I try make rpi-update but after it my raspberry couldn't boot. How can i update rpi and fix it to boot raspberry properly ? (I assuem that after update rpi this issue with hdmi black screen will be fixed like you wrote in previous posts)

@JamesH65
Copy link
Contributor

Please use the forums for tech support questions - rpi-update loads bleeding edge test firmware, you should not really be using it and there hasn't been any changes on this topic for a month or two.

@frankgould
Copy link

frankgould commented Jun 7, 2020

I am having this same RPi4B problem again with the latest Arch Linux ARM 4.19 upgrade and I don't know why. It's now blanking the screen with backlight on instead of turning off the HDMI monitor when using dpms 10 10 10 and xset s off. Is there something I'm doing wrong or I need to do to fix this again?
Edit: Nevermind. I found my problem was I needed to set the right screen driver in /boot/config.txt as follows: dtoverlay=vc4-fkms-v3d. It is now working again. Mybad.

mkreisl added a commit to xbianonpi/xbian-package-firmware that referenced this issue Jan 12, 2021
- firmware: Unicam: Request frequency of 250MHz when running camera use cases

- firmware: arm_loader: Fix UART unmapping

- firmware: uart1: Revert to the old core-frequency-locking method
  See: #1267

- firmware: arm_loader: Provide a sensible device_tree_end default
  See: #1259

- firmware: mmal_ril: Fix size reported on ENOSPC error
  See: #1269

- firmware: hvs: Trigger the EOLn timer at the field rate when interlaced
  See: #1227

- firmware: bootloader_state: Add support for a custom TFTP prefix parameter

- firmware: arm_loader: GIC stub => 2711 stu
- See: #1255

- firmware: arm_loader: Add os_prefix option
  See: raspberrypi/linux#3237

- firmware: Add support for arbitrary memory specification

- firmware: arm_loader: Fix explicit kernel name handling
  See: #1277

- firmware: Added a new display power mailbox call

- firmware: Update display_power gencmd with optional display id
  See: raspberrypi/linux#3050

- firmware: Remove legacy pkgconfig to avoid Mesa conflicts
  See: raspberrypi/userland#585

- firmware: Update display_power gencmd with optional display id

- firmware: sysman: Fix unsafe check for h264 being enabled
  See: popcornmix/omxplayer#749

- firmware: platform: Reduce absolute microvolts threshold to 500000

- firmware: tv_server: Also initialise ts queue on composite
  See: https://forum.kodi.tv/showthread.php?tid=348205

- firmware: Loop to init hotplug

- firmware: hdmi: Change HDMI state machine and BVB clocks as turbo clocks

- firmware: hdmi: Add EOF timeout to unjam failed mode changes

- firmware: platform: Differentiate between boostable and turbo clocks

- firmware: arm_dt: Set WL_ON and BT_ON from .dtb

- firmware: Fixup chosing of bit depth in legacy graphics
  See: raspberrypi/linux#3331

- firmware: vec: Setup WideScreen Signalling outside of copy protection
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=256489

- firmware: Add global reset mailbox

- firmware: 2711: De-couple start.elf clock setup from the bootloader

- firmware: scaler: Correct defines for SCALER_POS0_START_Y_[MASK|SHIFT] (HVS4)

- firmware: platform: Fix missing HDMI PHY power down bit

- firmware: Reduce voltage as part of DVFS

- firmware: arm-loader: Inherit 2711 mac-address from the bootloader
  See: http://git/vc4/vc4/merge_requests/687

- firmware: arm_loader: Respect all required frequencies when throttling

- firmware: Fixup vcgencmd display_power return values

- firmware: platform: Allow fixed voltage with avs_disable=1

- firmware: EMMC: Use PLLD for EMMC for 250MHz host-clock
  See: #1289

- firmware: platform: Round down effective frequencies when they exceed max
  See: #1290

- firmware: arm_loader: Pass video mode via kernel command for composite
  See: #1285

- firmware: Fix lens shading table generation buglet
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=190586&start=75#p1534672

- firmware: hdmi: Use RB2 timing for 2560x1440@60 if pixel clock is 241.5 MHz

- firmware: arm_dt: Look for ethernet0 before ethernet

- firmware: arm_dt: Set PCIe dma-ranges from memory size

- firmware: hdmi: HDMI SM clock must not run slower than audio MAI clock
  See: #1295

- firmware: arm_loader: Pass video mode via kernel command for composite (master)
  See: #1285

- firmware: power: Use Pi4 PMIC values on Pi3+

- firmware: Fix filtered handling of array variables
  See: #1296

- firmware: Update libfdt to v1.5.1+
  See: raspberrypi/userland#582

- firmware: dtoverlay: Extend DT parameter syntax

- firmware: memorymap: Include FW revision in start.elf

- firmware: Fixup for vcgencmd display_power
  See: #1224

- firmware: Add hdmi_wifi_pixel_freq_adj config option

- firmware: Revert mmal: Support 64 bit clients
  See: raspberrypi/userland#586

- firmware: arm_dt/dtoverlay fixes for ARM side camera driver power control

- firmware: arm_ldconfig: Support multiple initramfs files
  See: #1318

- firmware: Add support for backlight enable

- firmware: master: arm_ldconfig: Support multiple initramfs files
  See: #1318

- firmware: power: Make pmicrd/pmicwr available to all

- firmware: platform: Only throttle down from arm_freq

- firmware: platform: Bump desired ring osc to 3.7 on Pi3/CM3

- firmware: arm_loader: Add 2ms delay before resetting SD_IO

- firmware: isp/tuner: Resetting to a lamp mode cancels manual_gains_used_

- firmware: board_info: Fix uninitialised phy_addr handling in network boot

- firmware: IL video_decode: Default to H264 as MPEG4 isn't supported

- firmware: IL egl_render: Fail the create on Pi4

- firmware: arm_dispmanx: Column pitch for YUV10COL is in lines not bytes

- firmware: platform: 2711: Also add chicken bits to dvfs voltage

- firmware: MMAL / video_render: Allow column stride to be set on column formats

- firmware: vc_image/video_decode: Move +16 lines for di_adv from vc_image to decoder

- firmware: platform: 2711: Support overclocking gpu frequencies
  See: #1290

- firmware: gencmd: Fix measure_clock name for CLOCK_OUTPUT_108

- firmware: mmal isp: Remote alignment requirements for RGB24 formats

- firmware: Add missing flags for VC_IMAGE_PROP_YUVUV_4K_CHROMA_ALIGN

- firmware: platform: Compromise on gpu overclock settings
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=262649&start=100#p1610362

- firmware: Add the ability to export labels from overlays

- firmware: loader: 4-byte align initramfs blocks
  See: #1318

- firmware: vd3/video_decode: Do not add 16 lines of context when video is 1920 tall
  See: #1334

- firmware: Allow use of 24 bit framebuffers
  See: #1338

- firmware: arm_loader: Add non-os_prefix cmdline.txt fallback

- firmware: board_info: Set board-info memory size according to SDRAM mode registers

- firmware: arm_loader: Treat min frequencies as optional
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=264786

- firmware: arm_loader: Add overvoltage_delta for manufacture tests

- firmware: Support Isp stats and params

- firmware: arm_loader: Make EMMC2 dma-ranges patch more tolerant

- firmware: bootromfs: Delete unwanted assert

- firmware: usb_eth: Increase timeouts for TFTP requests and retransmit ACK

- firmware: isp component: rtos_common_mem: Fix handle acquire usage with wrap handles

- firmware: il: video_render: Require 4k chroma alignment on YUVUV transpose
  See: #1334

- firmware: vc_image: Don't align the YUVUV pitch to SDRAM pages if not aligning to 4k
  See: raspberrypi/linux#3492

- firmware: isp component: rtos_common_mem: Fix smallalloc test in mem_handle_acquire_if_valid

- firmware: platform: 2711: Make chicken-bit pip size vary with pmic quantum

- firmware: USB device boot for CM4

- firmware: arm_loader: Add SET_LAUNCH_VPU1 mailbox message

- firmware: il: camera: Add config.txt param awb_auto_is_greyworld for NoIR camera
  See: #1167

- firmware: arm_loader: Provisional support for high peris

- firmware: arm_loader: Only add margins to cmdline if non-zero

- firmware: clock: Support clock_measure_pll on pi0-3

- firmware: platform: Back to CLOCK_PLL_CHAN_CPER for emmc on pi0-3

-  firmware: gpu_server: Fixup after LAUNCH_VPU1 commit

- firmware: power: Add a notch to compensate for trim on 2835

- firmware: isp/tuner: Resetting to a lamp mode cancels manual_gains_used_ (master)

- firmware: armstubs: Rebuild with latest source

- firmware: arm_loader: Avoid resetting the GPIO expander

- firmware: vcos_genversion: Fix up legacy variant names

- firmware: dtoverlay: Add overlay_map functionality
  See: raspberrypi/linux#3520

-  firmware: isp_tuner: Add in the slave AWB tuner handling

- firmware: arm_dt: Apply os_prefix to device_tree= files

- firmware: clock_2711: Fix PLL analog setup

- firmware: board_info: Also include CM3+ for pmic trait
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=267576&start=25#p1643032

- firmware: Switch to building from common firmware branch

- firmware: isp: make AGC metering respect the (digital zoom) crop region

- firmware: Avoid linking in khronos on Pi4

- firmware: clock: Reset PLLC after switching VPU to OSC

- firmware: arm_loader: Make 4GB available if arm_peri_high

- firmware: arm_loader: Complete arm_peri_high support
  See: #1374

- firmware: board_info: Split Model B into rev1 and rev2
  See: raspberrypi/linux#3537

- firmware: power: Clamp voltage to platform limits for all power supplies

- firmware: isp: Ensure lens shading (LS) is enabled when a valid LS table is received

- firmware: otp: Fix advanced boot row definition

- firmware: bootcode: Fix issue booting with webcams

- firmware: isp: fix ISP component to return non-zero focus FoMs

- firmware: Fix for IMX477 focal length, f_number and aperture

- firmware: Update firmware for USB MSD boot

- firmware: platform: Fix overflow on high arm overclocks

- firmware: video_encode: Add option to include header bytes with frame

- firmware: DSI display: Close I2C handle if the display doesn't probe

- firmware: mmal/vc: Add mapping for OMX_IndexConfigBufferStall / MMAL_PARAMETER_VIDEO_STALL_THRESHOLD
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=70&t=273123&p=1655481

- firmware: hdmi: Request an I2C interrupt for EDID reading

- firmware: i2c: Move using_interrupt flag into periph_setup

- firmware: camera: Latency reduction for captures

- firmware: IL camera fixes for reduced startup time

- firmware: mmal_ril: Correct a use of portdef.video to portdef.image

- firmware: vc_image: SDRAM page alignment is optional for YUV10_COL
  See: https://forum.libreelec.tv/thread/21985-noise-artefacts-when-playing-back-4k-hevc-video-on-rpi4-le-9-2-1-no-problems-on/

- firmware: imx477: Correct the logic for extending hblank on long exposures

- firmware: il: isp: Ensure HR output is active and ISP is open before starting a frame

- firmware: isp_ctrl: Fail in start_[raw|yuv]_frame if ISP is not idle
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=275489

- firmware: vcfw: Fix PMIC max voltage
  See: https://forum.libreelec.tv/thread/22097-libreelec-leia-9-2-3

- firmware: ISP raw14 and mono input, 16bpc YUV output. Camera subsystem not messing with GPIO0

- firmware: isp: fix assert from initial setting of ISP denoise parameters

- firmware: arm_ldconfig: Don't pad initramfs files
  See: #1395

- firmware: board_info: Add and use BT_FLOWCONTROL trait

- firmware: logging: Add missing checks for uart_output_enabled

- firmware: host_applications: Install debug_sym.h

- firmware: logging: Inherit uart_2ndstage config from the bootloader

- firmware: Fix Pi4 regression in previous build

- firmware: platform: Resolve BT flow control contention
  See: Hexxeh/rpi-firmware#227

- firmware: hdmi: Limit the valid CEA modes to those defined in the table
  See: https://forum.libreelec.tv/thread/22135-regression-raspberry-pi-3-hdmi-output-broken-after-upgrade-to-9-2-x

- firmware: imx477: Add switch to allow switching of on-sensor DPC

- firmware: hdmi: Set HD_CTL_WHOLSMP and HD_CTL_CHALIGN_SET
  See: https://forum.kodi.tv/showthread.php?tid=354589

- firmware: arm_ldconfig: Honour the kernel8 text offset
  See: #1415

- firmware: jpeghw: Skip repeated 0xFF padding bytes between markers
  See: RPi-Distro/vlc#8

- firmware: arm_loader: Allow interlaced HDMI modes from FKMS
  See: raspberrypi/linux#3698

- firmware: arm_loader: Limit rather than reject boosts with disable_auto_turbo

- firmware: i2c: Clearing the TA bit may time out
  See: #1422

- firmware: arm_loader: Add an accelerated memmove

- firmware: arm_loader: memmove kernel to preferred text_offset
  See: #1421

- firmware: filesystem: Fix GPT regression on USB after SD fix
  See: #1420

- firmware: arm_loader: Don't enable the ARM USB IRQ
  See: raspberrypi/linux#3703

- firmware: hdmi: Remove M2MC/BVB min turbo clock request

- firmware: IL: camera: Fix stereoscopic pool allocations

- firmware: arm_loader: Add support for double clock/pixel_rep for FKMS
  See: raspberrypi/linux#3725

- firmware: scalerlib: Set the default chroma location for YUV10 to match 8bit

- firmware: scalerlib: Set chroma_vrep correctly for YUV10COL

- firmware: isp: check the hi-res resize filter mode when the input crop changes

- firmware: arm_loader: Knock 1.7 seconds off boot time
  See: #1375

- firmware: Imx477 external sync signals

- firmware: bootloader: Some tweaks for LED, UART, USB timeouts

- firmware: platform: Avoid vco issue with low arm_freq_min on Pi0-3
  See: #1431

- firmware: arm_loader: Don't try to load to 0 a.k.a. NULL
  See: #1445

- firmware: armstub7: Configure the top 32 STB interrupts

- firmware: dispmanx: Remove elements cleanly that are totally offscreen negatively
  See: raspberrypi/linux#3735

- firmware: hdmi: Set the altered mode, not the caller's mode
  See: #1446

- firmware: dt-blob: Declare CM4 GPIO expander pins

- firmware: clocks: Make frequency_t 64-bit

- firmware: Revert frequency_t: Make 64-bit

- firmware: ISP/tuner: Increase max exposure time for fixed ISO modes on IMX219 and 477
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=281603

- firmware: sdhost_arasan: Ignore DCRC after CMD12
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=282928

- firmware: firmware: frequency_t: Make 64-bit

- firmware: pi4: allow pllb changes while running
  See: #1431

- firmware: board_info: Give the CUSTOM boards the PMIC_NCP6343 trait

- firmware: dispmanx/displays: Allow both DPI and DSI displays simultaneously

- firmware: imx477: Release the I2C semaphore once finished, not before

- firmware: clock: Allow overclocking pllb
  See: raspberrypi/linux#3823

- firmware: hdmi/edid: Reduce the bias to all but the first detailed timing

- firmware: hdmi/edid: Add option to ignore any odd horizontal timings on Pi4

- firmware: sdcard: Hybrid MBR - only select GPT if it is the first primary partition
  See: #1465

- firmware: audioplus: Avoid broken audio when requesting hdmi audio device when using composite display
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=283639

- firmware: platform: Add support for SCB clock and set to 250MHz

- firmware: Revert arm_loader: Move first call to set_turbo after arm->start

- firmware: arm_ldconfig: GZIP-compressed ARMv8 kernel support

- firmware: arm_ldconfig: Restore the fallback load address
  See: #1467

- firmware: ilcamera: Disable timeouts on trigger sink devices

- firmware: genet: Flush RBUF/TBUF and clear mac-address on stop
  See: raspberrypi/linux#3850

- firmware: dmalib: Add support for 40-bit 2d memcpy

- firmware: sdcard: Reduce SD read overhead

- firmware: sdhost_arasan: Increase time threshold before suspend

- firmware: video_decode: Only shutdown codec on both ports being disabled

- firmware: vc_image_helper: Avoid misaligned exception due to uninitialised pointer

- firmware: arm_loader: Make arm clock accesses only see their own boosts
  See: #1469

- firmware: arm_loader: enable simple_fb iff there is a display
  See: raspberrypi/linux#3878

- firmware: arm_loader: Mark V3D early boost as for the ARM
  See: #1469

- firmware: arm_loader: Update armstubs with those from PR 117
  See: raspberrypi/tools#117

- firmware: Revert sdcard: Reduce SD read overhead

- firmware: arm_loader: Add GET/SET_VPU_VECTOR mailbox calls

- firmware: arm_ldconfig: Don't invalidate the dcache for most of memory
  See: #1445

- firmware: arm_loader: Allow arm to see force_turbo and uart boosts

- firmware: hdmi: Timeout HDMI EDID reads

- firmware: pwm_sdm: move modulator to VPU0
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=195178&p=1723639

- firmware: Add tryboot mechanism to provide a fallback if an OS upgrade fails

- firmware: camplus: stills_denoise: Release the VRF between iterations

- firmware: vc_image: Further fixup of fix_alignment
  See: #1334

- firmware: arm_loader: Support large PCIe window with <8GB RAM
  See: https://www.raspberrypi.org/forums/viewtopic.php?p=1759627#p1759627

- firmware: filesys: Close the brfs from filesys_power(..., 0)

- firmware: platform: Avoid vco issue with low arm_freq_min on Pi0-3
  See: #1431

- firmware: video_encode: Allow level 5.0 and 5.1
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=291447

- firmware: xhci: Don't reset BCM2711 XHCI from filesys in start.elf

- firmware: bootcode.bin: Add support for tryboot

- firmware: Switch DA9121 PMIC to PWM mode when ARM > 600 MHz

- firmware: arm_dt: Handle parent interrupt controllers when masking

- firmware: config: Add cm4 and pi400 config section filters

- firmware: MMAL/IL/ISP component: Set the ISP boost frequency once on open

- firmware: sdcard: Remove legacy NOOBS support to support booting from primary partition 4

- firmware: arm_loader: Move 2711 RAM to PCIe address 16GB

- firmware: video_decode: Add parameter to disable timestamp validation

- firmware: Imx477 camera tuning fixes
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=291032#p1770287
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=291032&start=25#p1771066

- firmware: Use DMA40 for PWM audio

- firmware: imx477: Replace existing 720p120 mode with a new 1332x990 120fps mode

- firmware: arm_loader: Allow max_framebuffers=0 to disable framebuffers
  See: #1507

- firmware: dmalib: Allow sdcard to borrow channel 6
  See: #1511
  See: Hexxeh/rpi-firmware#251
  See: https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=294932

- firmware: DSI interrupt fixes, and HDMI SM clock for deep colour

- firmware: dmalib: Keep 40-bit DMA clear of L2 alias

- firmware: audioplus: Fix hang when switching destination
  See: #1516

- firmware: HAT/I2C updates

- firmware: MMAL/IL: Add support for the 16bpp Bayer/Grey raw 10/12/14 formats

- firmware: Revert firmware: HAT/I2C updates

- firmware: firmware: MMAL/IL: Add support for the 16bpp Bayer/Grey raw 10/12/14 formats

- Firmware: undo previous reverts
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

No branches or pull requests