[U-Boot] [U-Boot, v4, 1/1] avb: add support for named persistent values

[Simon Glass]

HI Igor,

On Wed, 13 Feb 2019 at 16:39, Igor Opaniuk <igor.opaniuk at linaro.org> wrote:
>
> Hi Simon,
>
> Seems that there is an issue in dm test framework (if understood
> everything correctly),
>
> I've noticed that dm_root is updated when dm tests are being invoked,
> and that's why the new tee udevice is allocated, consequently, the
> second invocation of probe in tee driver occurs.
> In dm_test_init() dm_root is re-inited with NULL (then it populates
> new dm tree for from scratch, probing all devices), and I can't find
> where it is done(or if it's done at all) a proper removal/cleanup of
> devices from the previous dm tree before this dm_test initialization
> is invoked (I've added a conditional breakpoint for removal of
> previously allocated tee device, and it's never being called):

I don't believe we clean up the devices when running tests.

It looks like there are some static variables in the sandbox optee
driver. That is not correct - everything should be stored in
driver-private or uclass-private data so that it goes away.

Maybe that is the problem?

[..]

Regards,
Simon