public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Lee Revell <rlrevell@joe-job.com>
Cc: john stultz <johnstul@us.ibm.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch] API for timer hooks
Date: Wed, 17 Aug 2005 20:21:06 +0400	[thread overview]
Message-ID: <430363F2.7090009@aknet.ru> (raw)
In-Reply-To: <1124244580.30036.5.camel@mindpipe>

Hello.

Lee Revell wrote:
> Wow, your driver implements bass and treble controls by varying the
> frequency of the timer interrupt.  That's a neat hack, but I'd expect it
> to raise a few eyebrows if it's submitted for mainline...
I realized that some time ago, and now,
even though the code it still there,
the treble/bass controls are no longer
exported to the mixer. The driver now
works on a fixed frequency. Well, you
can still select one of the two base
frequencies, but if need be, I can
disallow also this. I am willing to
reduce the requirements as much as possible,
as long as it will help getting the thing
in, but perhaps allowing a single higher
frequency, or allowing just any frequency,
is pretty much the same task, and doesn't
look achievable within the currently existing
timer API anyway.


  reply	other threads:[~2005-08-17 16:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13 13:36 [rfc][patch] API for timer hooks Stas Sergeev
2005-08-15 17:19 ` john stultz
2005-08-16 20:21   ` Stas Sergeev
2005-08-16 22:24     ` Nish Aravamudan
2005-08-17 16:10       ` Stas Sergeev
2005-08-17  2:09     ` Lee Revell
2005-08-17 16:21       ` Stas Sergeev [this message]
2005-08-17 16:40         ` Lee Revell
2005-08-17 17:41           ` Stas Sergeev
2005-08-17 23:16             ` Lee Revell
2005-08-18 16:59               ` Stas Sergeev
2005-08-18 17:07                 ` Lee Revell

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=430363F2.7090009@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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