diff options
author | Hao Wu <hao.a.wu@intel.com> | 2019-02-12 11:19:26 +0800 |
---|---|---|
committer | Hao Wu <hao.a.wu@intel.com> | 2019-02-25 16:33:49 +0800 |
commit | 2df8798274429cb40da4cabc551ef6efa07c1a99 (patch) | |
tree | 70d0b2ad6dd80299d464e7f7480d2022fc476b08 /BaseTools/Source/Python/AutoGen/GenPcdDb.py | |
parent | 68a4e15e149771f36ba58b3adcef9b2981a4eda6 (diff) | |
download | edk2-2df8798274429cb40da4cabc551ef6efa07c1a99.tar.gz edk2-2df8798274429cb40da4cabc551ef6efa07c1a99.tar.bz2 edk2-2df8798274429cb40da4cabc551ef6efa07c1a99.zip |
MdeModulePkg/UfsBlockIoPei: Correct use of 'DeviceIndex' in BlkIO PPI
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1474
Within UfsBlockIoPei, the current implementation of the Block IO(2)
services:
UfsBlockIoPeimGetMediaInfo
UfsBlockIoPeimReadBlocks
UfsBlockIoPeimGetMediaInfo2
UfsBlockIoPeimReadBlocks2
does not handle the input parameter 'DeviceIndex' properly.
According to both of the PI spec and the function description comments:
> DeviceIndex Specifies the block device to which the function wants
> to talk. ... This index is a number from one to
> NumberBlockDevices.
But current codes incorrectly treat the valid range of 'DeviceIndex' as 0
to (NumberBlockDevices - 1).
This commit is to address this issue.
Cc: Jian J Wang <jian.j.wang@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Hao Wu <hao.a.wu@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/AutoGen/GenPcdDb.py')
0 files changed, 0 insertions, 0 deletions