diff options
| author | Mark Hasemeyer <markhas@chromium.org> | 2024-01-02 14:07:28 -0700 |
|---|---|---|
| committer | Rob Herring <robh@kernel.org> | 2024-01-10 19:45:37 -0600 |
| commit | 5b202c250acd8dd1df9fcc8e6319ecd83d69923a (patch) | |
| tree | ee4645b497606ca1c5461fb349bcda1ed34fb6bc /tools/testing/selftests/bpf/prog_tests/recursion.c | |
| parent | 4dde83569832f9377362e50f7748463340c5db6b (diff) | |
dt-bindings: power: Clarify wording for wakeup-source property
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@mail.gmail.com/
Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
Link: https://lore.kernel.org/r/20240102140734.v4.4.I1016a45ac9e8daf8a9ebc9854ab90ec3542e7c30@changeid
Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/recursion.c')
0 files changed, 0 insertions, 0 deletions