diff options
author | Yanfei Xu <yanfei.xu@intel.com> | 2024-08-28 16:42:30 +0800 |
---|---|---|
committer | Dave Jiang <dave.jiang@intel.com> | 2024-09-09 11:33:44 -0700 |
commit | 99bf0eebc75c9085440d6dca014724e7e49b5116 (patch) | |
tree | 1a72d3e3899d682dc38bad0ba2d223e62b06cd5a /tools/perf/scripts/python/gecko.py | |
parent | 5c6e3d5a5da118be2ae074bd70d111994147c708 (diff) |
cxl/pci: Check Mem_info_valid bit for each applicable DVSEC
In theory a device might set the mem_info_valid bit for a first range
after it is ready but before as second range has reached that state.
Therefore, the correct approach is to check the Mem_info_valid bit for
each applicable DVSEC range against HDM_COUNT, rather than only for the
DVSEC range 1. Consequently, let's move the check into the "for loop"
that handles each DVSEC range.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Yanfei Xu <yanfei.xu@intel.com>
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
Link: https://patch.msgid.link/20240828084231.1378789-4-yanfei.xu@intel.com
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions