[PATCH V2] firmware: ti_sci: Scan all device instances when releasing exclusive devices

[Kumar, Udit]

On 4/11/2025 4:53 PM, Nishanth Menon wrote:
> 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

Its good to do clean up. But IMO, problem you described mainly will be seen

in unified DM case.

> 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.


Anyway, patch LTGM irrespective of DM type


Thanks