From: "Habil Eren Türker" <habilerenturker@gmail.com>
To: clemens@ladisch.de, corbet@lwn.net, tglx@kernel.org
Cc: skhan@linuxfoundation.org, anna-maria@linutronix.de,
frederic@kernel.org, linux-doc@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
"Habil Eren Türker" <habilerenturker@hotmail.com>
Subject: [PATCH] docs: timers: hpet: Modernize file references and document userspace API
Date: Sat, 26 Sep 2026 20:06:49 +0300 [thread overview]
Message-ID: <20260926170649.6346-1-habilerenturker@hotmail.com> (raw)
The current HPET documentation contains outdated 'file:' prefixes for
source tree references, which breaks proper rendering and hyperlink
generation under the modern Sphinx-based documentation ecosystem.
Fix this by modernizing the paths using the standard literal backticks
formatting. Additionally, add a dedicated 'Userspace API and ioctl
Commands' section to clearly document the supported ioctl interfaces
extrapolated from include/uapi/linux/hpet.h and samples/timers/hpet_example.c,
including the layout of struct hpet_info.
Signed-off-by: Habil Eren Türker <habilerenturker@hotmail.com>
---
Documentation/timers/hpet.rst | 31 +++++++++++++++++++++++++++++--
1 file changed, 29 insertions(+), 2 deletions(-)
diff --git a/Documentation/timers/hpet.rst b/Documentation/timers/hpet.rst
index c9d05d3ca..e21a6185b 100644
--- a/Documentation/timers/hpet.rst
+++ b/Documentation/timers/hpet.rst
@@ -23,8 +23,35 @@ The driver supports detection of HPET driver allocation and initialization
of the HPET before the driver module_init routine is called. This enables
platform code which uses timer 0 or 1 as the main timer to intercept HPET
initialization. An example of this initialization can be found in
-arch/x86/kernel/hpet.c.
+``arch/x86/kernel/hpet.c``.
The driver provides a userspace API which resembles the API found in the
RTC driver framework. An example user space program is provided in
-file:samples/timers/hpet_example.c
+``samples/timers/hpet_example.c``
+
+Userspace API and ioctl Commands
+================================
+
+* ``HPET_IE_ON`` / ``HPET_IE_OFF``
+ Enables or disables the interrupt generation for the timer channel.
+
+* ``HPET_INFO``
+ It is used to query the capabilities and current status of the HPET.
+ When the ioctl call is made, the kernel populates the ``struct hpet_info``
+ structure and returns it to userspace:
+
+ .. code-block:: c
+
+ struct hpet_info {
+ unsigned long hi_ireqfreq; /* Hz */
+ unsigned long hi_flags; /* information */
+ unsigned short hi_hpet;
+ unsigned short hi_timer;
+ };
+
+* ``HPET_EPI`` / ``HPET_DPI``
+ Enables or disables periodic interrupts. When activated, the timer triggers continuously at the specified frequency.
+
+* ``HPET_IRQFREQ``
+ Sets the interrupt frequency for the periodic timer.
+ This request takes an unsigned long argument specifying the desired frequency in Hz.
--
2.47.3
next reply other threads:[~2026-09-26 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 17:06 Habil Eren Türker [this message]
2026-09-26 17:52 ` [PATCH] docs: timers: hpet: Modernize file references and document userspace API Jonathan Corbet
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=20260926170649.6346-1-habilerenturker@hotmail.com \
--to=habilerenturker@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=clemens@ladisch.de \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=habilerenturker@hotmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=x86@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