arm64: dts: qcom: sc7280: Enable cros-ec-spi as wake source
The cros_ec driver currently assumes that cros-ec-spi compatible device nodes are a wakeup-source even though the wakeup-source property is not defined. Some Chromebooks use a separate wake pin, while others overload the interrupt for wake and IO. With the current assumption, spurious wakes can occur on systems that use a separate wake pin. It is planned to update the driver to no longer assume that the EC interrupt pin should be enabled for wake. Add the wakeup-source property to all cros-ec-spi compatible device nodes to signify to the driver that they should still be a valid wakeup source. Reviewed-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Mark Hasemeyer <markhas@chromium.org> Link: https://lore.kernel.org/r/20240102140734.v4.15.I7ea3f53272c9b7cd77633adfd18058ba443eed96@changeid Signed-off-by: Bjorn Andersson <andersson@kernel.org>
This commit is contained in:
committed by
Bjorn Andersson
parent
f172a341ec
commit
a4b28b9ecc
@@ -548,6 +548,7 @@ ap_ec_spi: &spi10 {
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&ap_ec_int_l>;
|
||||
spi-max-frequency = <3000000>;
|
||||
wakeup-source;
|
||||
|
||||
cros_ec_pwm: pwm {
|
||||
compatible = "google,cros-ec-pwm";
|
||||
|
||||
@@ -19,6 +19,7 @@ ap_ec_spi: &spi10 {
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&ap_ec_int_l>;
|
||||
spi-max-frequency = <3000000>;
|
||||
wakeup-source;
|
||||
|
||||
cros_ec_pwm: pwm {
|
||||
compatible = "google,cros-ec-pwm";
|
||||
|
||||
Reference in New Issue
Block a user