Re: [PATCH] drm/gma500: Fix call trace when psb_gem_mm_init() fails

2023-08-25 Thread suijingfeng
Hi, On 2023/8/25 14:54, Patrik Jakobsson wrote: On Fri, Jul 28, 2023 at 02:58:55AM +0800, Sui Jingfeng wrote: Because the gma_irq_install() is call after psb_gem_mm_init() function, when psb_gem_mm_init() fails, the interrupt line haven't been allocated. Yet the gma_irq_uninstall() is called i

Re: [PATCH] drm/gma500: Fix call trace when psb_gem_mm_init() fails

2023-08-24 Thread Patrik Jakobsson
On Fri, Jul 28, 2023 at 02:58:55AM +0800, Sui Jingfeng wrote: > Because the gma_irq_install() is call after psb_gem_mm_init() function, > when psb_gem_mm_init() fails, the interrupt line haven't been allocated. > Yet the gma_irq_uninstall() is called in the psb_driver_unload() function > without ch

[PATCH] drm/gma500: Fix call trace when psb_gem_mm_init() fails

2023-07-27 Thread Sui Jingfeng
Because the gma_irq_install() is call after psb_gem_mm_init() function, when psb_gem_mm_init() fails, the interrupt line haven't been allocated. Yet the gma_irq_uninstall() is called in the psb_driver_unload() function without checking if checking the irq is registered or not. The calltrace is app