From: Lee Revell <rlrevell@joe-job.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Thibaut VARENE <T-Bone@parisc-linux.org>,
alsa-devel@lists.sourceforge.net,
parisc-linux@lists.parisc-linux.org, kyle@parisc-linux.org
Subject: Re: [parisc-linux] [PATCH] Support for AD1889 PCI Soundchip
Date: Thu, 18 Aug 2005 13:12:34 -0400 [thread overview]
Message-ID: <1124385155.5973.20.camel@mindpipe> (raw)
In-Reply-To: <Pine.HPX.4.33n.0508171249360.19860-200000@studcom.urz.uni-halle.de>
On Thu, 2005-08-18 at 17:35 +0200, Clemens Ladisch wrote:
> > > +/* keep track of some hw registers */
> > > struct ad1889_register_state {
> > > u16 reg; /* reg setup */
> > > u32 addr; /* dma base address */
> > > - u16 rate; /* sample rate */
> > > - unsigned long pos; /* last recorded DMA buffer position
> */
> > > - unsigned long buf; /* period # */
> > > unsigned long size; /* DMA buffer size */
> > > - unsigned long count; /* period size, aka nb bytes sent in
> the current DMA transfer */
> >
> > reading the patch through webmail doesn't help a lot getting a grasp
> > of its whole but i wonder if we could still find some debugging
> > purposes for these values. Remember this driver is work in
> progress ;)
>
> Those fields just aren't used anymore; anything interesting is in the
> chip's registers.
Isn't it still useful to maintain a cached copy of the register state
for suspend/resume purposes?
Lee
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-18 17:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 19:16 [PATCH] Support for AD1889 PCI Soundchip Thibaut VARENE
2005-07-29 19:20 ` [parisc-linux] " Thibaut VARENE
2005-08-03 13:46 ` Takashi Iwai
2005-08-04 13:30 ` [parisc-linux] " Clemens Ladisch
2005-08-11 15:18 ` Clemens Ladisch
2005-08-12 2:14 ` Kyle McMartin
2005-08-12 7:17 ` Clemens Ladisch
2005-08-17 1:51 ` Kyle McMartin
2005-08-17 13:50 ` Clemens Ladisch
2005-08-17 9:10 ` Thibaut VARENE
2005-08-18 15:35 ` Clemens Ladisch
2005-08-18 17:12 ` Lee Revell [this message]
2005-08-19 17:46 ` Grant Grundler
2005-08-19 17:53 ` Takashi Iwai
2005-08-20 1:36 ` Grant Grundler
2005-08-22 11:03 ` Takashi Iwai
2005-08-23 0:13 ` Grant Grundler
2005-08-23 9:11 ` Takashi Iwai
2005-08-28 12:57 ` Thibaut VARENE
2005-08-31 2:26 ` Kyle McMartin
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=1124385155.5973.20.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=T-Bone@parisc-linux.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=kyle@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.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