-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Backport HEVC decoder as submitted to linux-media as v2 #6666
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
Conversation
I think we want ffmpeg update public (or the second /dev/videoN node) before merging this. |
I'd asked @jc-kynesim whether the FFmpeg side had been released on Friday, and he'd replied
I don't know if that happened. |
fd2db7e
to
031a382
Compare
60e5cbd
to
d024995
Compare
a4a537b
to
0b989c6
Compare
Rebased and reworked so that the client is required to pass the column height in the pitch field if the modifier is DRM_FORMAT_MOD_BROADCOM_SAND128. It does require removing one validation clause in the core DRM code if a modifier is set, and that may be an argument with upstream (I'll look forward to it!) We can now have a single new path that works with both DRM and EGL (as of Mesa 24.2.5) rendering. This still has the revert of the new pixel format so that it shouldn't change anything on systems without Mesa 24. |
0b989c6
to
931822d
Compare
e984a1f
to
0f48fde
Compare
This reverts commit d7c70b0.
This reverts commit 9629d77.
This reverts commit 64ff380.
By default when the last request object is completed, the whole request completes as well. But sometimes you want to manually complete a request in a driver, so add a manual complete mode for this. In req_queue the driver marks the request for manual completion by calling media_request_mark_manual_completion, and when the driver wants to manually complete the request it calls media_request_manual_complete(). Signed-off-by: Hans Verkuil <[email protected]>
Manually complete the requests: this tests the manual completion code. Signed-off-by: Hans Verkuil <[email protected]>
Keep track of the number of requests and request objects of a media device. Helps to verify that all request-related memory is freed. Signed-off-by: Hans Verkuil <[email protected]>
The Raspberry Pi HEVC decoder uses a tiled format based on columns for 8 and 10 bit YUV images, so document them as NV12MT_COL128 and NV12MT_10_COL128. Signed-off-by: Dave Stevenson <[email protected]>
Add V4L2_PIXFMT_NV12MT_COL128 and V4L2_PIXFMT_NV12MT_10_COL128 to describe the Raspberry Pi HEVC decoder NV12 multiplanar formats. Signed-off-by: Dave Stevenson <[email protected]>
Adds a binding for the HEVC decoder found on the BCM2711 / Raspberry Pi 4, and BCM2712 / Raspberry Pi 5. Signed-off-by: Dave Stevenson <[email protected]>
The BCM2711 and BCM2712 SoCs used on Rapsberry Pi 4 and Raspberry Pi 5 boards include an HEVC decoder block. Add a driver for it. Signed-off-by: John Cox <[email protected]> Signed-off-by: Dave Stevenson <[email protected]>
Add the configuration information for the HEVC decoder. Signed-off-by: Dave Stevenson <[email protected]>
931822d
to
892b669
Compare
Rebased. AFAIK this is ready to go. The only question is whether Libreelec folks are aware of the change, and have picked up the base FFmpeg changes before taking this kernel. |
I've let them know (but they'd already been following this PR). |
Ah - this breaks hevc decode with kodi21 in RPiOS, as it uses embedded ffmpeg (kodi21 wants a newer ffmpeg). It looks like the older kodi package still works as that uses system ffmpeg. I'm happy with this being merged for now (we can ensure kodi21 is updated before this kernel reaches apt). |
While kodi 20 worked on a Pi5. I can't play hevc on a Pi4.
@HiassofT also saw similar behaviour is libreelec. Suprisingly Pi 5 is okay with the same hevc file (sony football one). |
}; | ||
&hevc_dec { | ||
reg = <0x0 0x7eb10000 0x0 0x1000>, /* INTC */ | ||
<0x0 0x7eb00000 0x0 0x10000>; /* HEVC */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
INTC and HEVC are swapped compared to bcm2711.dtsi - this breaks HEVC on RPi4.
likely the hevc_dec override should just be dropped as reg is set in bcm2711.dtsi anyways EDIT: scratch that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Yes it is needed as size-cells
differs between upstream and downstream, but the swapping is wrong.
Signed-off-by: Dave Stevenson <[email protected]>
For downstream only, add back in the legacy single planar SAND formats. Signed-off-by: Dave Stevenson <[email protected]>
Upstream will take the multi-planar SAND format, but add back in the downstream single planar variant for backwards compatibility Signed-off-by: Dave Stevenson <[email protected]>
Signed-off-by: Dave Stevenson <[email protected]>
Signed-off-by: Dave Stevenson <[email protected]>
vc4's debugfs support was updated with drm_debugfs_entry whilst BCM2712 support was in progress, and missed that the lookup in vc6_hvs_debugfs_dlist still followed the old pattern. Correct that lookup to avoid an invalid dereference. Fixes: f7af8ae ("drm/vc4: hvs: Add support for BCM2712 HVS") Signed-off-by: Dave Stevenson <[email protected]>
The SAND handling had been using what was believed to be a runtime parameter in the modifier, however that has been clarified that all permitted variants of the modifier must be advertised, so making it variable wasn't practical. With a rationalisation of how the producers of this format are configured, we can switch to a variant that doesn't have as much variation, and can be configured such that only 2 options are required. Add a modifier with value 0 to denote that the height of the luma column matches the buffer height, and chroma column will be half that due to YUV420. A modifier of 1 denotes that the height of the luma column still matches the buffer height, but the chroma column height is the same. This can be used to replicate the previous behaviour. Signed-off-by: Dave Stevenson <[email protected]>
The SAND modifier with height 0 is now using the provided pitch as the column stride, but the UBM allocation needs to be done based on the plane width. Recompute the width in these conditions. Signed-off-by: Dave Stevenson <[email protected]>
Pitch has no meaning if the modifier isn't DRM_FORMAT_MOD_LINEAR as there is no guarantee that the value passed follows the pattern that pitch * height = size. Remove that check from framebuffer_check. Signed-off-by: Dave Stevenson <[email protected]>
To avoid user complaints that /dev/video0 isn't their USB webcam, add downstream patch that allows setting the preferred video device number. Signed-off-by: Dave Stevenson <[email protected]>
Supporting GL rendering of the new HEVC decoder pixel formats requires Mesa 24.2.5 or later. There are a couple of minor issues holding up switching to Mesa 24. Drop the new pixel formats from enum_fmt so that FFMpeg will use the older ones that earlier versions of Mesa do support. Signed-off-by: Dave Stevenson <[email protected]>
892b669
to
69a3783
Compare
Updated to correct bcm2711-rpi-ds.dtsi |
I'm happy for this to be merged if somebody can confirm that Pi 4 is working now. |
Yes - hevc is working on Pi4 for me with this update. |
kernel: Backport HEVC decoder as submitted to linux-media as v2 See: raspberrypi/linux#6666 kernel: Add the wifimac overlay See: raspberrypi/linux#6707 kernel: configs: Add GPIO_FXL6408=m See: raspberrypi/linux#6711 kernel:dtoverlays: Add adxl345 to i2c-sensor See: raspberrypi/linux#6712 kernel: overlays: Use current I2C Sysfs in README examples See: raspberrypi/linux#6713 kernel: dts: Remove the power key debounce on Pi 500
kernel: Backport HEVC decoder as submitted to linux-media as v2 See: raspberrypi/linux#6666 kernel: Add the wifimac overlay See: raspberrypi/linux#6707 kernel: configs: Add GPIO_FXL6408=m See: raspberrypi/linux#6711 kernel:dtoverlays: Add adxl345 to i2c-sensor See: raspberrypi/linux#6712 kernel: overlays: Use current I2C Sysfs in README examples See: raspberrypi/linux#6713 kernel: dts: Remove the power key debounce on Pi 500
This PR:
This doesn't work against the existing FFmpeg as it is looking for extra flags to identify a device that it thinks can decode HEVC. @jc-kynesim was going to release his updated FFmpeg that handles this, otherwise I can look at whether we can expose a second /dev/videoN node that adds in those flags as an interim.
This wants more thorough testing, hence looking to push it to rpi-6.12.y.