Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Karsten Wiese <annabellesgarden@yahoo.de>,
	alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH]snd-usb-usx2y 0.8.7: Use macro usb_maxpacket() for portability
Date: Thu, 09 Dec 2004 11:14:02 +0100	[thread overview]
Message-ID: <s5his7baidx.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0412090914550.3423@pnote.perex-int.cz>

At Thu, 9 Dec 2004 09:18:04 +0100 (CET),
Jaroslav wrote:
> 
> On Wed, 8 Dec 2004, Takashi Iwai wrote:
> 
> > At Tue, 7 Dec 2004 23:01:51 +0100,
> > Karsten Wiese wrote:
> > > 
> > > >>>>
> > > Summary: hwdep interface for pcm data.
> > > 
> > > Implements "rawusb" pcm data transfer through hwdep interface:
> > > The usb_hc moves pcm data from/into memory via DMA.
> > > That memory is mmaped by jack's usx2y driver.
> > > Jack's usx2y driver is the first/last executable code to read/write pcm data.
> > > Read/write is a combination of power of 2 period shaping and float/int conversation.
> > > Compared to standard alsa/jack we leave out power of 2 period shaping
> > > inside snd-usb-usx2y which needs memcpy() and additional buffers.
> > > As a side effect possible unwanted pcm-data coruption resulting of
> > > standard alsa's snd-usb-usx2y period shaping scheme falls away.
> > > Result is sane jack operation at buffering schemes down to 128frames, 2 periods.
> > > Also changed Kconfig file, so snd-usb-usx2y is only available for X86, PPC or ALPHA platforms,
> > > as on others DMA-memory isn't mmapable.
> > > 
> > > Signed-off-by: Karsten Wiese <annabellesgarden@yahoo.de>
> > > <<<<
> > 
> > Thanks, applied to the CVS tree now.
> > Please check later whether it works for you...
> 
> My feeling is that it's against all we're trying to do with the PCM 
> interface. Cannot we extend/optimize the current PCM API?

Don't worry, in the new patch, the hwdep does actually only mmap.  The
others are done with the usual PCM API.

The implementation is still a bit tricky, IMO, though.
We can generalize this if there would be more wide needs for such
stuff.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-09 10:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 12:19 [PATCH]snd-usb-usx2y 0.8.7: Use macro usb_maxpacket() for portability Karsten Wiese
2004-12-02 14:42 ` Takashi Iwai
2004-12-06 22:15   ` Karsten Wiese
2004-12-07 11:48     ` Takashi Iwai
2004-12-07 22:01       ` Karsten Wiese
2004-12-08 19:32         ` Takashi Iwai
2004-12-09  8:18           ` Jaroslav Kysela
2004-12-09 10:14             ` Takashi Iwai [this message]
2004-12-09 12:06           ` Karsten Wiese
2004-12-10 15:57             ` Rui Nuno Capela
2004-12-10 16:13               ` Takashi Iwai
2004-12-10 17:42                 ` Rui Nuno Capela
2004-12-10 17:53                   ` Takashi Iwai
2004-12-10 18:18                     ` Rui Nuno Capela
2004-12-10 18:24                       ` Takashi Iwai
2004-12-10 21:08                         ` Rui Nuno Capela

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=s5his7baidx.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=annabellesgarden@yahoo.de \
    --cc=perex@suse.cz \
    /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