[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbSs-vebvchxx-Tg+O5CUF5M3vZf-iytuW=ZECnHb2anA@mail.gmail.com>
Date: Fri, 8 Dec 2023 13:54:21 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Stefan Eichenberger <eichest@...il.com>
Cc: nick@...anahar.org, dmitry.torokhov@...il.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...on.dev, linux-input@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Stefan Eichenberger <stefan.eichenberger@...adex.com>
Subject: Re: [PATCH v1 1/2] dt-bindings: input: atmel,maxtouch: add
poweroff-in-suspend property
On Thu, Dec 7, 2023 at 12:13 PM Stefan Eichenberger <eichest@...il.com> wrote:
> From: Stefan Eichenberger <stefan.eichenberger@...adex.com>
>
> Add a new property to indicate that the device should be powered off in
> suspend mode.
>
> Signed-off-by: Stefan Eichenberger <stefan.eichenberger@...adex.com>
(...)
> + atmel,poweroff-in-suspend:
> + description: |
> + When this property is set, all supplies are turned off when the system is
> + going to suspend.
> + type: boolean
wakeup-source:
type: boolean
As Krzysztof says it seems you are describing an operating system feature.
I can't help but wonder: shouldn't that pretty much be the default behaviour
if wakeup-source is *not* specified?
I.e. the property kind of describes !wakeup-source.
Yours,
Linus Walleij
Powered by blists - more mailing lists