From: Torben Hohn <torbenh@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
linuxpps@ml.enneenne.com, Torben Hohn <torbenh@gmx.de>
Subject: [PATCH 2/5] RFC genirq: add function to retrieve timestamp from irqdesc
Date: Mon, 21 Mar 2011 12:59:17 +0100 [thread overview]
Message-ID: <1300708760-27910-2-git-send-email-torbenh@gmx.de> (raw)
In-Reply-To: <1300708760-27910-1-git-send-email-torbenh@gmx.de>
this is probably not useful.
and will be superceded by other functions.
its just here to ilustrate my initial idea.
Signed-off-by: Torben Hohn <torbenh@gmx.de>
---
kernel/irq/manage.c | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index e9df1f0..adbf6c9 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1176,3 +1176,12 @@ int request_any_context_irq(unsigned int irq, irq_handler_t handler,
return !ret ? IRQC_IS_HARDIRQ : ret;
}
EXPORT_SYMBOL_GPL(request_any_context_irq);
+
+void retreive_irq_timestamp(unsigned int irq, struct timespec *ts)
+{
+ struct irq_desc *desc = irq_to_desc(irq);
+
+ *ts = desc->last_timestamp;
+}
+EXPORT_SYMBOL_GPL(retreive_irq_timestamp);
+
--
1.7.2.3
next prev parent reply other threads:[~2011-03-21 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 11:59 [PATCH 1/5] RFC genirq: Add IRQ timestamping Torben Hohn
2011-03-21 11:59 ` Torben Hohn [this message]
2011-03-21 11:59 ` [PATCH 3/5] RFC genirq: save irq timestamps in void *dev_id Torben Hohn
2011-03-21 11:59 ` [PATCH 4/5] RFC genirq: allow dynamic switching of timestamping irqs Torben Hohn
2011-03-21 11:59 ` [PATCH 5/5] RFC genirq: enforce dev_id to be struct timespec * with IRQF_TIMESTAMP Torben Hohn
2011-03-21 12:43 ` [PATCH 1/5] RFC genirq: Add IRQ timestamping torbenh
2011-03-22 2:33 ` john stultz
2011-03-22 13:32 ` torbenh
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=1300708760-27910-2-git-send-email-torbenh@gmx.de \
--to=torbenh@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxpps@ml.enneenne.com \
--cc=tglx@linutronix.de \
/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®