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
already marked active, so it assumes this can no longer be controlled
by software and is marked internally as reserved and HLOS can no
longer control these instances. This defeated the purpose of
ti_sci_cmd_release_exclusive_devices.
NOTE: This scheme works just fine if the FIT has just a single dtb as
the info->dev_list is upto date.
To fix this, let us make ti_sci_cmd_release_exclusive_devices scan the
all registrations of tisci instances and cleanup all exclusive devices
that have ever been registered.
As part of this, change the prototype of release_exclusive_devices to
drop the handle since that has no further meaning now.
Though this issue was identified on AM64-sk, this can be present in
other builds which use multi-fit-dtb for R5 SPL startup.
[..]
