On 06/08, Javier Martinez Canillas wrote:
Hello Florian,
On 6/8/22 11:26, Florian Fainelli wrote:
On 6/3/2022 11:26 AM, Peter Robinson wrote:
This is a follow up from my v4 patchset. The power management pieces have been split out to a separate independent set of patches by Stefan [1]. This version 5 of the DRM patches are independent and given the V3D driver has been upstream for some time the two patches to enable it in defconfigs can be taken at anytime independent of the enablement for the Raspberry Pi 4.
I've tested this using mesa 22.0.x and Wayland/Gnome on Fedora 36, it's more or less stable with basic testing.
Changes since v5:
- Update the DT compatible to match the others that were updated
- Adjust the Kconfig help text
- Add review tags
Changes since v4:
- Fixes for device tree and bindings
- Split out the power management changes into an independent set
- Rebase to 5.18
- Individual changes in patches
I can take the last 3 patches through the Broadcom ARM SoC pull request, but the first three should probably go via the DRM tree unless you want me to merge them all?
I can merge the first 3 patches through the drm-misc tree. Can I get an ack from you for those ?
The changes are independent so there's no need for an immutable branch or any kind of cross tree coordination.
Hi Javier,
I'm not sure if you're suggesting here to apply the entire series as it is now.
I'm not able to have a functional kernel from arm defconfig, only for arm64. I'd like to have this issue clarified before merge this serie. I tried multi_v7_defconfig on raspbian 32-bits and got a kernel panic. Things work better when using downstream bcm2711_defconfig.
If you have an idea of what is going on, please, let me know. I can try again and I'll be okay on merging it. Otherwise, let's wait for more inputs to have a better picture of the situation.
Thanks,
Melissa
-- Best regards,
Javier Martinez Canillas Linux Engineering Red Hat