On 11:04-20250411, Kumar, Udit wrote: > Hi Nishanth, > > Sorry for basic question > > On 4/7/2025 5:45 PM, Nishanth Menon wrote: > > [..] This creates a problem when Device Manager(DM) firmware starts up later > > on in the boot process and identifies that this instance of i2c is > > Do we need to do clean up, where DM is loaded as different binary . > > As I understand this cleanup is needed, where DM is running along with > SPL/R5 > > or I am missing something
The cleanup makes sense whether we use split or unified DM. The resources R5SPL uses may or may not be used further down the chain of software (eeprom was an example where we read and cache the data for further downstream steps to use). We should never be leaving a messy system behind (and consequences as a result). This is the reason we cleanup the exclusively held devices during the boot phase before remote cores are started up. We already do this cleanup. which is good, the trouble with multi-DTB FIT image is that the cleanup is partial, which is what this patch attempts to solve. -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
