From: phucduc.bui@gmail.com
To: krzk+dt@kernel.org, geert+renesas@glider.be
Cc: 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,
phucduc.bui@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
magnus.damm@gmail.com, robh@kernel.org,
wsa+renesas@sang-engineering.com
Subject: [PATCH v4 0/2] Input: st1232 - add system wakeup support
Date: Mon, 9 Mar 2026 07:03:17 +0700 [thread overview]
Message-ID: <20260309000319.74880-1-phucduc.bui@gmail.com> (raw)
From: bui duc phuc <phucduc.bui@gmail.com>
This patch series adds support for using the Sitronix ST1232
touchscreen as a wakeup source on the Armadillo800EVA board.
Patch 1 documents the generic wakeup-source property in the
Devicetree binding for the ST1232 touchscreen controller.
Patch 2 enables the wakeup-source property in the ST1232
touchscreen node for the Armadillo800EVA board, allowing touch
events to wake the system from suspend.
Verified functionality
* The "power/wakeup" sysfs attribute is present for the device.
* The system resumes correctly from 'mem' and 'freeze' states when the
touchscreen is touched.
Additional test information
Demo video showing wakeup from suspend:
https://youtu.be/POJhbguiA7A
Kernel config and boot logs:
https://gist.github.com/BuiDucPhuc/ac7d5d732658ca293af4323ad04accca
Changes in v4:
*Drop patch 3 as the I2C core already performs the initialization,
registration, and management of the wakeup interrupt, making the
implementation in the driver redundant.
The original intention of patch 3 was to expose active_count,
event_count, and wakeup_count to user space. However, this is not
necessary since the R8A7740 SoC has some specific characteristics
in its wakeup interrupt handling.
Moreover, modifying this driver could potentially affect other SoCs
sharing the same driver, so the patch is removed.
*Going back to v1 design.
*Update the cover letter
Changes in v3:
* Patch 3: Removed debug dev_info() log messages for a cleaner
production-ready implementation.
* No changes to Patch 1 and Patch 2.
* Link :
https://lore.kernel.org/all/20260306111912.58388-1-phucduc.bui@gmail.com/
Changes in v2
* Drop description for wakeup-source property as suggested by
Krzysztof Kozlowski.
* Updated commit messages for clarity.
* Added driver-side wakeup handling in st1232.c.
* Link :
https://lore.kernel.org/all/20260306104025.43970-1-phucduc.bui@gmail.com/
v1
*Link:
https://lore.kernel.org/all/20260305113512.227269-1-phucduc.bui@gmail.com/
This series depends on the following patch which has been
submitted but not yet merged:
drm: shmobile: Fix blank screen after resume when LCDC is stopped
Link: https://lore.kernel.org/all/20260226054035.30330-1-phucduc.bui@gmail.com/
bui duc phuc (2):
dt-bindings: input: touchscreen: sitronix,st1232: Add wakeup-source
arm: dts: renesas: r8a7740-armadillo800eva: Add wakeup-source to
st1232
.../bindings/input/touchscreen/sitronix,st1232.yaml | 4 ++++
arch/arm/boot/dts/renesas/r8a7740-armadillo800eva.dts | 1 +
2 files changed, 5 insertions(+)
--
2.43.0
next reply other threads:[~2026-03-09 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 0:03 phucduc.bui [this message]
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 ` [PATCH v4 0/2] Input: st1232 - add system wakeup support Wolfram Sang
2026-03-11 10:38 ` 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=20260309000319.74880-1-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.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=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox