[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <170483310084.3189837.7384632761496015121.robh@kernel.org>
Date: Tue, 9 Jan 2024 14:45:02 -0600
From: Rob Herring <robh@...nel.org>
To: Mark Hasemeyer <markhas@...omium.org>
Cc: Rob Herring <robh+dt@...nel.org>, Tzung-Bi Shih <tzungbi@...nel.org>, devicetree@...r.kernel.org, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Raul Rangel <rrangel@...omium.org>, LKML <linux-kernel@...r.kernel.org>, Sudeep Holla <sudeep.holla@....com>, Konrad Dybcio <konrad.dybcio@...aro.org>, Conor Dooley <conor+dt@...nel.org>, Andy Shevchenko <andriy.shevchenko@...el.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH v4 04/24] dt-bindings: power: Clarify wording for
wakeup-source property
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@mail.gmail.com/
> Signed-off-by: Mark Hasemeyer <markhas@...omium.org>
> ---
>
> (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!
Powered by blists - more mailing lists