diff options
| author |   Ohad Sharabi <osharabi@habana.ai> | 2021-10-17 09:00:43 +0300 |
|---|---|---|
| committer |   Oded Gabbay <ogabbay@kernel.org> | 2021-12-26 08:59:03 +0200 |
| commit | bfd5110682ca75cece49fe0e3f5ef478ec43c9ae (patch) | |
| tree | 6c158550f7a016410dae2eb0d61ec5e287a7491d /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | habanalabs: print va_range in vm node debugfs (diff) | |
| download | wireguard-linux-bfd5110682ca75cece49fe0e3f5ef478ec43c9ae.tar.xz wireguard-linux-bfd5110682ca75cece49fe0e3f5ef478ec43c9ae.zip | |
habanalabs: revise and document use of boot status flags
The boot status flag "SRAM available" can be set by f/w Linux (in the
general case) or by f/w uboot (in some specific debug scenario) but
never by f/w preboot.
Hence, when polling the boot status flags in the preboot stage we do not
want to poll on "SRAM Avialable".
The special case in which uboot set this flag is when we are running
special debug scenario without Linux. In this case, at some point during
the boot, the uboot relocates its code to the DRAM and then set the
specified flag.
Signed-off-by: Ohad Sharabi <osharabi@habana.ai>
Reviewed-by: Oded Gabbay <ogabbay@kernel.org>
Signed-off-by: Oded Gabbay <ogabbay@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions