Matt Delco has posted comments on this change. ( https://review.coreboot.org/28073 )
Change subject: mainboard/google/nocturne: turn off cams in D3
......................................................................
Patch Set 1:
> Patch Set 1:
> In this case, that means the _OFF in power resource will be called
> when transit into to D3hot state.
That'd be true with this change, but prior to this change having a value in _PR3 means to keep the device on in D3hot. Is there any reason to provide power to the devices outside of D0?
> the corresponding object to set the device into a deeper Dx must also be declared, and vice versa.
That just says it needs to be declared, so I could stick in an empty _PS3 but nobody bothers to do that even if it's a stronger fit to the spec requirements.
--
To view, visit https://review.coreboot.org/28073
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: Id52c2499c3b7577f03395cc9ca2460f25b80e13f
Gerrit-Change-Number: 28073
Gerrit-PatchSet: 1
Gerrit-Owner: Matt Delco <delco(a)chromium.org>
Gerrit-Reviewer: Lijian Zhao <lijian.zhao(a)intel.com>
Gerrit-Reviewer: Matt Delco <delco(a)chromium.org>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Lance Zhao <lance.zhao(a)gmail.com>
Gerrit-Comment-Date: Tue, 14 Aug 2018 18:37:55 +0000
Gerrit-HasComments: No
Gerrit-HasLabels: No
Hannah Williams has posted comments on this change. ( https://review.coreboot.org/28060 )
Change subject: intel/common/block: Fix issues found by klockwork
......................................................................
Patch Set 2:
> Patch Set 1:
>
> (1 comment)
>
> > Martin, What tool are you using for this code scan - we're not
> > getting these "soc issues" flagged, using Klocwork Static Code
> > Analysis tool?
> > We are getting different "warnings" in chip.c and gspi.c files.
>
> These are generated using clang's scan-build tool:
> https://clang-analyzer.llvm.org/scan-build.html
>
> We also run coverity's stataic analysis on a bi-weekly basis. That output is here:
> https://scan.coverity.com/projects/coreboot?tab=overview
> That finds still different issues in soc/intel.
I have a feeling that since static.c gets deleted from the emerge build, so KW does not see the dev_root structure and hence we have been getting errors reported for possible NULL access for dev = dev_find_path
--
To view, visit https://review.coreboot.org/28060
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I5e7caa15a3911e05ff346d338493673af5318a51
Gerrit-Change-Number: 28060
Gerrit-PatchSet: 2
Gerrit-Owner: John Zhao <john.zhao(a)intel.com>
Gerrit-Reviewer: John Zhao <john.zhao(a)intel.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: AndreX Andraos <andrex.andraos(a)intel.com>
Gerrit-CC: Balaji Manigandan <balaji.manigandan(a)intel.com>
Gerrit-CC: Hannah Williams <hannah.williams(a)intel.com>
Gerrit-CC: Martin Roth <martinroth(a)google.com>
Gerrit-Comment-Date: Tue, 14 Aug 2018 18:23:50 +0000
Gerrit-HasComments: No
Gerrit-HasLabels: No
Lucas Chen has uploaded this change for review. ( https://review.coreboot.org/28079
Change subject: eve: Support PL1 override option
......................................................................
eve: Support PL1 override option
AltOS DPTF prefers MMIO to control the PL1 setting. However, MSR PL1 also
contributes to the decision of the max PL1 power. In the current design,
the lower value takes effect. In order to align MMIO and MSR settings, a
tdp_pl1_override option is added to override the MSR PL1 limitation.
BRANCH=eve
BUG=b:73133864
TEST=1. Write PL1 override setting in devicetree.cb
2. Verify the MSR PL1 limitation is set from TAT.
Change-Id: I35b8747ad3ee4c68c30d49a9436aa319360bab9b
Signed-off-by: Lucas Chen <lucas.chen(a)quanta.corp-partner.google.com>
---
M src/soc/intel/skylake/chip.h
M src/soc/intel/skylake/cpu.c
2 files changed, 6 insertions(+), 2 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/79/28079/1
diff --git a/src/soc/intel/skylake/chip.h b/src/soc/intel/skylake/chip.h
index a147d92..8cef686 100644
--- a/src/soc/intel/skylake/chip.h
+++ b/src/soc/intel/skylake/chip.h
@@ -99,6 +99,8 @@
/* PL2 Override value in Watts */
u32 tdp_pl2_override;
+ /* PL1 Override value in Watts */
+ u32 tdp_pl1_override;
/* SysPL2 Value in Watts */
u32 tdp_psyspl2;
diff --git a/src/soc/intel/skylake/cpu.c b/src/soc/intel/skylake/cpu.c
index 5535ec6..417c4bc 100644
--- a/src/soc/intel/skylake/cpu.c
+++ b/src/soc/intel/skylake/cpu.c
@@ -117,7 +117,7 @@
msr_t msr = rdmsr(MSR_PLATFORM_INFO);
msr_t limit;
unsigned int power_unit;
- unsigned int tdp, min_power, max_power, max_time, tdp_pl2;
+ unsigned int tdp, min_power, max_power, max_time, tdp_pl2, tdp_pl1;
u8 power_limit_1_val;
struct device *dev = SA_DEV_ROOT;
config_t *conf = dev->chip_info;
@@ -154,7 +154,9 @@
/* Set long term power limit to TDP */
limit.lo = 0;
- limit.lo |= tdp & PKG_POWER_LIMIT_MASK;
+ tdp_pl1 = ((conf->tdp_pl1_override == 0) ?
+ tdp : (conf->tdp_pl1_override * power_unit));
+ limit.lo |= (tdp_pl1 & PKG_POWER_LIMIT_MASK);
/* Set PL1 Pkg Power clamp bit */
limit.lo |= PKG_POWER_LIMIT_CLAMP;
--
To view, visit https://review.coreboot.org/28079
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-MessageType: newchange
Gerrit-Change-Id: I35b8747ad3ee4c68c30d49a9436aa319360bab9b
Gerrit-Change-Number: 28079
Gerrit-PatchSet: 1
Gerrit-Owner: Lucas Chen <lucas.chen(a)quanta.corp-partner.google.com>
Gerrit-Reviewer: Wei Shun Chang <wei.shun.chang(a)intel.com>