Searched hist:a6e0afc29a8bd2c1f8cde87043d69c3e77ef23d5 (Results 1 – 2 of 2) sorted by relevance
| /linux/arch/arm/boot/dts/nvidia/ |
| H A D | tegra124-venice2.dts | diff a6e0afc29a8bd2c1f8cde87043d69c3e77ef23d5 Tue Jan 02 22:07:29 CET 2024 Mark Hasemeyer <markhas@chromium.org> ARM: tegra: 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.
Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
Signed-off-by: Thierry Reding <treding@nvidia.com>
|
| H A D | tegra124-nyan.dtsi | diff a6e0afc29a8bd2c1f8cde87043d69c3e77ef23d5 Tue Jan 02 22:07:29 CET 2024 Mark Hasemeyer <markhas@chromium.org> ARM: tegra: 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.
Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
Signed-off-by: Thierry Reding <treding@nvidia.com>
|