From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: phucduc.bui@gmail.com
Cc: krzk+dt@kernel.org, geert+renesas@glider.be, krzk@kernel.org,
krzysztof.kozlowski@oss.qualcomm.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, dmitry.torokhov@gmail.com,
hechtb@gmail.com, javier.carrasco@wolfvision.net,
jeff@labundy.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
magnus.damm@gmail.com, robh@kernel.org
Subject: Re: [PATCH v4 0/2] Input: st1232 - add system wakeup support
Date: Wed, 11 Mar 2026 00:09:46 +0100 [thread overview]
Message-ID: <abCkulmW8XDXkXiT@shikoro> (raw)
In-Reply-To: <20260309000319.74880-1-phucduc.bui@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
Hi,
> Demo video showing wakeup from suspend:
> https://youtu.be/POJhbguiA7A
Nice video! You really put some effort here, kudos.
Really awesome seeing Linux 7 on this old platform :)
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-10 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 0:03 [PATCH v4 0/2] Input: st1232 - add system wakeup support phucduc.bui
2026-03-09 0:03 ` [PATCH v4 1/2] dt-bindings: input: touchscreen: sitronix,st1232: Add wakeup-source phucduc.bui
2026-03-10 23:35 ` Dmitry Torokhov
2026-03-11 4:25 ` [PATCH v4 1/2] dt-bindings: input: touchscreen: phucduc.bui
2026-03-09 0:03 ` [PATCH v4 2/2] arm: dts: renesas: r8a7740-armadillo800eva: Add wakeup-source to st1232 phucduc.bui
2026-03-10 23:08 ` Wolfram Sang
2026-03-11 4:22 ` [PATCH v4 2/2] arm: dts: renesas: r8a7740-armadillo800eva: phucduc.bui
2026-03-13 8:41 ` [PATCH v4 2/2] arm: dts: renesas: r8a7740-armadillo800eva: Add wakeup-source to st1232 Geert Uytterhoeven
2026-03-10 23:09 ` Wolfram Sang [this message]
2026-03-11 10:38 ` [PATCH v4 0/2] Input: st1232 - add system wakeup support phucduc.bui
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=abCkulmW8XDXkXiT@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=hechtb@gmail.com \
--cc=javier.carrasco@wolfvision.net \
--cc=jeff@labundy.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=phucduc.bui@gmail.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.