video: simplefb: Remove DM_FLAG_PRE_RELOC flag
When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be bound before relocation. However due to a bug in the DM core, the flag only takes effect when devices are statically declared via U_BOOT_DEVICE(). This bug has been fixed recently by commit "dm: core: Respect drivers with the DM_FLAG_PRE_RELOC flag in lists_bind_fdt()", but with the fix, it has a side effect that all existing drivers that declared DM_FLAG_PRE_RELOC flag will be bound before relocation now. This may expose potential boot failure on some boards due to insufficient memory during the pre-relocation stage. To mitigate this potential impact, the following changes are implemented: - Remove DM_FLAG_PRE_RELOC flag in the driver, if the driver only supports configuration from device tree (OF_CONTROL) - Keep DM_FLAG_PRE_RELOC flag in the driver only if the device is statically declared via U_BOOT_DEVICE() - Surround DM_FLAG_PRE_RELOC flag with OF_CONTROL check, for drivers that support both statically declared devices and configuration from device tree Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
		
							parent
							
								
									ef329a6a73
								
							
						
					
					
						commit
						e3245e4254
					
				| 
						 | 
					@ -68,5 +68,4 @@ U_BOOT_DRIVER(simple_video) = {
 | 
				
			||||||
	.id	= UCLASS_VIDEO,
 | 
						.id	= UCLASS_VIDEO,
 | 
				
			||||||
	.of_match = simple_video_ids,
 | 
						.of_match = simple_video_ids,
 | 
				
			||||||
	.probe	= simple_video_probe,
 | 
						.probe	= simple_video_probe,
 | 
				
			||||||
	.flags	= DM_FLAG_PRE_RELOC,
 | 
					 | 
				
			||||||
};
 | 
					};
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue