summaryrefslogtreecommitdiff
path: root/src/device
diff options
context:
space:
mode:
authorYu-Ping Wu <yupingso@chromium.org>2022-08-09 15:54:05 +0800
committerPaul Fagerburg <pfagerburg@chromium.org>2022-09-22 15:14:40 +0000
commit514277f7462e338c41c27e37198725923128d039 (patch)
tree710ce0baff29bd1a04799f69ff8e7790b35b8100 /src/device
parenta19ff6dea3ef01ee49a0f34cac019edc25041ce6 (diff)
mb/google/cherry: Initialize PCIe by SKU encoding
All cherry boards (tomato, dojo) share the same SKU ID encoding, in the sense that a device has NVMe storage if and only if the BIT(1) of SKU ID is set (otherwise eMMC). Therefore, instead of hard coding the list of NVMe (PCIe) SKU IDs, we check the BIT(1) to decide whether to initialize PCIe. In addition, in preparation for UFS devices coming in the future, reserve BIT(3) (which is unset for all of current SKUs) for them. BUG=b:237953117, b:233327674 TEST=emerge-cherry coreboot BRANCH=cherry Change-Id: I9b30338645a87f29f96a249808b90f1ec16f82df Signed-off-by: Yu-Ping Wu <yupingso@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/66580 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Yidi Lin <yidilin@google.com> Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Diffstat (limited to 'src/device')
0 files changed, 0 insertions, 0 deletions