From: Manuel Traut <manuel.traut@mt.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-input@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Markus Burri <markus.burri@mt.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: input: matrix_keypad - add wakeup-source property
Date: Fri, 28 Feb 2025 07:42:04 +0100 [thread overview]
Message-ID: <Z8FavNuODoIVepuj@mt.com> (raw)
In-Reply-To: <Z8EMI9ALqYY72VBV@google.com>
On Thu, Feb 27, 2025 at 05:06:43PM -0800, Dmitry Torokhov wrote:
> The driver recognizes standard "wakeup-source" property and there are
> DTS files using it. Add the property to the binding.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202502280105.REZ29MVg-lkp@intel.com/
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reviewed-by: Manuel Traut <manuel.traut@mt.com>
> ---
> .../devicetree/bindings/input/gpio-matrix-keypad.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> index 73bb153ed241..ebfff9e42a36 100644
> --- a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> +++ b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.yaml
> @@ -68,6 +68,8 @@ properties:
> Drive inactive columns during scan,
> default is to turn inactive columns into inputs.
>
> + wakeup-source: true
> +
> required:
> - compatible
> - row-gpios
> @@ -96,4 +98,6 @@ examples:
> 0x0001006A
> 0x0101001C
> 0x0201006C>;
> +
> + wakeup-source;
> };
> --
> 2.48.1.711.g2feabab25a-goog
>
>
> --
> Dmitry
next prev parent reply other threads:[~2025-02-28 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 1:06 [PATCH] dt-bindings: input: matrix_keypad - add wakeup-source property Dmitry Torokhov
2025-02-28 6:42 ` Manuel Traut [this message]
2025-02-28 18:49 ` Conor Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z8FavNuODoIVepuj@mt.com \
--to=manuel.traut@mt.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.burri@mt.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.