All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Question about kernel timers
Date: Tue, 25 Jul 2006 18:01:56 -0400	[thread overview]
Message-ID: <1153864917.25859.238.camel@mindpipe> (raw)

I am writing a driver in which every time some event occurs, two
single-shot timers must be scheduled.  This event could happen many
times per second so many of these timers can be pending at once.  Can
someone point me to an example of a driver that does something like
this?

All the ALSA drivers I can find that use timers have a single periodic
timer and use a struct timer_list in the card record.  However I think
this is not an option for me, as I must create new timers on the fly.

I've found that the kernel Oopses if you allocate a timer on the stack,
so I use kmalloc().  It seems to work, but leaks memory, as there's no
opportunity to free() all the timer_lists I'm creating on the fly.

Can I do this with a single struct timer_list?  Is it possible to
schedule multiple timers using add_timer() then changing the parameters
and add_timer() again?

It seems that this should be documented somewhere but it's not - LDD3
was no help.  All the examples were very simplistic.

Lee


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2006-07-25 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 22:01 Lee Revell [this message]
2006-07-28  1:18 ` Question about kernel timers Lee Revell
2006-07-28  7:01   ` Clemens Ladisch
2006-07-28  8:00 ` James Courtier-Dutton
2006-07-28 15:14   ` Lee Revell
2006-07-28 10:06 ` Takashi Iwai

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=1153864917.25859.238.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.