On Tue, 02 Jan 2024 14:07:28 -0700, Mark Hasemeyer wrote: > The wording in the current documentation is a little strong. The > intention was not to fix any particular interrupt as wakeup capable but > leave those details to the device. It wasn't intended to enforce any > rules as what can be or can't be a wakeup interrupt. > > Soften the wording to not mandate that the 'wakeup-source' property be > used, and clarify what it means when an interrupt is marked (or not > marked) for wakeup. > > Link: https://lore.kernel.org/all/ZYAjxxHcCOgDVMTQ@bogus/ > Link: https://lore.kernel.org/all/CAL_Jsq+MYwOG40X26cYmO9EkZ9xqWrXDi03MaRfxnV-+VGkXWQ@xxxxxxxxxxxxxx/ > Signed-off-by: Mark Hasemeyer <markhas@xxxxxxxxxxxx> > --- > > (no changes since v3) > > Changes in v3: > -Update commit title prefixes > > Changes in v2: > -New patch > > .../bindings/power/wakeup-source.txt | 18 +++++++++++------- > 1 file changed, 11 insertions(+), 7 deletions(-) > Applied, thanks!
