From: Takashi Iwai <tiwai@suse.de>
To: thomas charbonnel <thomas@undata.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsp fixes
Date: Thu, 27 Jan 2005 19:07:14 +0100 [thread overview]
Message-ID: <s5hekg6oiel.wl@alsa2.suse.de> (raw)
In-Reply-To: <1106761331.11426.17.camel@localhost>
Hi,
the following are some things I noticed in the patch:
> +#define HDSP_PRECISE_POINTER(xname, xindex) \
> { .iface = SNDRV_CTL_ELEM_IFACE_HWDEP, \
> .name = xname, \
> .index = xindex, \
> - .info = snd_hdsp_info_line_out, \
> - .get = snd_hdsp_get_line_out, \
> - .put = snd_hdsp_put_line_out \
> + .info = snd_hdsp_info_precise_pointer, \
> + .get = snd_hdsp_get_precise_pointer, \
> + .put = snd_hdsp_put_precise_pointer \
Do we need this as a control?
Isn't preceise_ptr reliable?
> + if (!is_9652 && !is_9632) {
> + /* we wait 2 seconds to let freshly inserted cardbus cards do their hardware init */
> + if ((1000 / HZ) < 2000) {
> + set_current_state(TASK_UNINTERRUPTIBLE);
> + schedule_timeout((2000 * HZ + 999) / 1000);
> + } else {
> + mdelay(2000);
> + }
You can use ssleep(2) here.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-27 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 17:42 hdsp fixes thomas charbonnel
2005-01-26 21:22 ` [Alsa-devel] " Fernando Lopez-Lezcano
2005-01-27 12:54 ` Free Ekanayaka
2005-01-27 11:10 ` Takashi Iwai
2005-01-27 18:07 ` Takashi Iwai [this message]
2005-01-27 21:42 ` thomas charbonnel
2005-01-28 14:23 ` 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=s5hekg6oiel.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=thomas@undata.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