diff options
author | Patrick Georgi <pgeorgi@google.com> | 2017-12-05 16:36:30 -0500 |
---|---|---|
committer | Patrick Georgi <pgeorgi@google.com> | 2017-12-08 11:38:05 +0000 |
commit | 9adcbfe486cb37ecbf38167ac13a502326f5863c (patch) | |
tree | c914045eb64e3dfd7dad105a1f58654c65ffd2e1 /util/kconfig | |
parent | 97ac471a7163cda6b48c477f221d788955ec1a7c (diff) | |
download | coreboot-9adcbfe486cb37ecbf38167ac13a502326f5863c.tar.xz |
device/pciexp_device: Set values numerically instead of as bitmask
As noted on linux-pci, we have a weird way to handling "value" and
"scale" fields that are supposed to contain numerical values: we encode
them as a bitfield.
Instead define the two fields (offset and mask) and use numbers.
Another issue, not fixed in this CL, is that we write hard-coded values
while these fields really need to contain the max() of acceptable delays
of the downstream devices. That way the controller can decide whether or
not to enter a deeper power management state. It's noted as a TODO.
Change-Id: I895b9fe2ee438d3958c2d787e70a84d73eaa49d2
Signed-off-by: Patrick Georgi <pgeorgi@google.com>
Found-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-on: https://review.coreboot.org/22740
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'util/kconfig')
0 files changed, 0 insertions, 0 deletions