soc/intel/jasperlake: Run pmc_set_acpi_mode() during .init in pmc_ops
pmc_set_acpi_mode will set EC SMI mask to 1 in the end. However google_chromeec_events_init will clear EC SMI mask. If google_chromeec_events_init is ran after pmc_set_acpi_mode, the EC SMI mask will be 0 in depthcharge and causes lidclose function not working. So, pmc_set_acpi_mode() should run after google_chromeec_events_init. This code is mainly from CB:42677 BUG=b:16338215 TEST=Close lid in depthcharge and the dut can be shutdown on waddledoo. Signed-off-by: Kane Chen <kane.chen@intel.com> Change-Id: I0f06e8b5da00eb05a34a6ce1de6d713005211c08 Reviewed-on: https://review.coreboot.org/c/coreboot/+/44563 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aamir Bohra <aamir.bohra@intel.com> Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Reviewed-by: Maulik V Vaghela <maulik.v.vaghela@intel.com>
This commit is contained in:
parent
9f4835ec2b
commit
000549266e
|
@ -78,8 +78,6 @@ static void pmc_init(struct device *dev)
|
||||||
pmc_set_power_failure_state(true);
|
pmc_set_power_failure_state(true);
|
||||||
pmc_gpe_init();
|
pmc_gpe_init();
|
||||||
|
|
||||||
pmc_set_acpi_mode();
|
|
||||||
|
|
||||||
config_deep_s3(config->deep_s3_enable_ac, config->deep_s3_enable_dc);
|
config_deep_s3(config->deep_s3_enable_ac, config->deep_s3_enable_dc);
|
||||||
config_deep_s5(config->deep_s5_enable_ac, config->deep_s5_enable_dc);
|
config_deep_s5(config->deep_s5_enable_ac, config->deep_s5_enable_dc);
|
||||||
config_deep_sx(config->deep_sx_config);
|
config_deep_sx(config->deep_sx_config);
|
||||||
|
@ -98,8 +96,23 @@ static void soc_pmc_read_resources(struct device *dev)
|
||||||
res->flags = IORESOURCE_IO | IORESOURCE_ASSIGNED | IORESOURCE_FIXED;
|
res->flags = IORESOURCE_IO | IORESOURCE_ASSIGNED | IORESOURCE_FIXED;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
static void soc_acpi_mode_init(struct device *dev)
|
||||||
|
{
|
||||||
|
/*
|
||||||
|
* pmc_set_acpi_mode() should be delayed until BS_DEV_INIT in order
|
||||||
|
* to ensure the ordering does not break the assumptions that other
|
||||||
|
* drivers make about ACPI mode (e.g. Chrome EC). Since it disables
|
||||||
|
* ACPI mode, other drivers may take different actions based on this
|
||||||
|
* (e.g. Chrome EC will flush any pending hostevent bits). Because
|
||||||
|
* JSL has its PMC device available for device_operations, it can be
|
||||||
|
* done from the "ops->init" callback.
|
||||||
|
*/
|
||||||
|
pmc_set_acpi_mode();
|
||||||
|
}
|
||||||
|
|
||||||
struct device_operations pmc_ops = {
|
struct device_operations pmc_ops = {
|
||||||
.read_resources = soc_pmc_read_resources,
|
.read_resources = soc_pmc_read_resources,
|
||||||
.set_resources = noop_set_resources,
|
.set_resources = noop_set_resources,
|
||||||
|
.init = soc_acpi_mode_init,
|
||||||
.enable = pmc_init,
|
.enable = pmc_init,
|
||||||
};
|
};
|
||||||
|
|
Loading…
Reference in New Issue