On 21/12/2023 00:54, 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> Please use subject prefixes matching the subsystem. You can get them for example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory your patch is touching. You nicely skipped all my filters... No need to resend to fix this, but fix it if sending a new version. Best regards, Krzysztof
