From: Markus Burri <markus.burri@mt.com>
To: linux-kernel@vger.kernel.org
Cc: Markus Burri <markus.burri@mt.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manuel Traut <manuel.traut@mt.com>, Marek Vasut <marex@denx.de>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
Markus Burri <markus.burri@bbv.ch>
Subject: [PATCH v3 0/7] rtc-rv8803: Implement timestamp trigger over event pins
Date: Tue, 13 May 2025 18:19:15 +0200 [thread overview]
Message-ID: <20250513161922.4064-1-markus.burri@mt.com> (raw)
The RV8901 RTC chip provides a function to store timestamp events.
There are three input pins (EVIN1-3) available for triggering.
The timestamp can be read to detect tamper alerts, for example.
This patch series extends the sysfs interface to enable and read the
timestamp events.
The data-sheet can be found here:
https://download.epsondevice.com/td/pdf/brief/RX8901CE_en.pdf
This series applies on 'linux-6.13~rc7'
Changes in V3:
* change permission for sysfs read to admin
* add device-tree bindings for event pin and buffer mode configuration
Changes in V2:
* remove separate patch for register definitions
* remove pin configuration over sysfs (use default settings)
* add sysfs documentation
* rework enable to simplify and remove big mutext scope
---
[V1] https://lore.kernel.org/lkml/20250110061401.358371-1-markus.burri@mt.com/
[V2] https://lore.kernel.org/lkml/20250116131532.471040-1-markus.burri@mt.com/
Markus Burri (7):
dt-bindings: rtc: add new type for epson,rx8901
rtc-rv8803: add new type for rv8901
rtc-rv8803: add tamper function to sysfs for rv8901
rtc-rv8803: extend sysfs to trigger internal ts-event
rtc-rv8803: extend sysfs to read status
dt-bindings: rtc-rv8803: add tamper detection property node
rtc-rv8803: make tamper function configurable via dt
.../ABI/testing/sysfs-class-rtc-tamper | 36 ++
.../devicetree/bindings/rtc/epson,rx8900.yaml | 42 +-
drivers/rtc/rtc-rv8803.c | 599 +++++++++++++++++-
3 files changed, 672 insertions(+), 5 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-class-rtc-tamper
base-commit: 92a09c47464d040866cf2b4cd052bc60555185fb
--
2.39.5
next reply other threads:[~2025-05-13 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:19 Markus Burri [this message]
2025-05-13 16:19 ` [PATCH v3 1/7] dt-bindings: rtc: add new type for epson,rx8901 Markus Burri
2025-05-13 16:19 ` [PATCH v3 2/7] rtc-rv8803: add new type for rv8901 Markus Burri
2025-05-13 16:19 ` [PATCH v3 3/7] rtc-rv8803: add tamper function to sysfs " Markus Burri
2025-05-13 16:19 ` [PATCH v3 4/7] rtc-rv8803: extend sysfs to trigger internal ts-event Markus Burri
2025-05-13 16:19 ` [PATCH v3 5/7] rtc-rv8803: extend sysfs to read status Markus Burri
2025-05-13 16:19 ` [PATCH v3 6/7] dt-bindings: rtc-rv8803: add tamper detection property node Markus Burri
2025-05-13 17:32 ` Rob Herring (Arm)
2025-05-14 12:38 ` Rob Herring
2025-05-13 16:19 ` [PATCH v3 7/7] rtc-rv8803: make tamper function configurable via dt Markus Burri
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=20250513161922.4064-1-markus.burri@mt.com \
--to=markus.burri@mt.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=manuel.traut@mt.com \
--cc=marex@denx.de \
--cc=markus.burri@bbv.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®