Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Thomas Charbonnel <thomas@undata.org>
Cc: Jesse Chappell <jesse@essej.net>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Alsa handling of spdif bits (was Re: Questions to HDSP users)
Date: Fri, 06 Feb 2004 14:32:35 +0100	[thread overview]
Message-ID: <s5h7jz08hak.wl@alsa2.suse.de> (raw)
In-Reply-To: <4023932E.3090107@undata.org>

At Fri, 06 Feb 2004 14:14:22 +0100,
Thomas Charbonnel wrote:
> 
> >>The problem I see and I dislike with this is that iec bits are 
> >>associated with playback. This is probably fine with most devices, but 
> >>not with hardware that can do hardware routing, where you may want to 
> >>route signal through the S/PDIF out with a certain bit combination - no 
> >>playback is involved here. I believe a generic iec bits handling 
> >>interface is a good thing, but is should not be affected by the card's 
> >>status. Any comment on this Takashi ?
> > 
> > 
> > well, in that case, the put callback of "IEC958 Playback Default"
> > should change the corresponding register value immediately, too.
> >
> 
> Ok, but it seems this can't be done with iecset,

hmm?  iecset will read/change "IEC958 Playback Default" (searching
both MIXER and PCM interfaces).
it doesn't change "IEC958 Playback PCM Stream", though.

>  so I'm back with my 
> question concerning amixer : all the 'value' fields of IEC ctls show a 
> question mark. Is this a problem with the driver ? If not what would be 
> the syntax to access those ctls ?

amixer doesn't handle IEC958 status properly.


> >>>An aside: this is also complicated because to open the device, the
> >>>channels item in the slave.pcm section must match the iobox in
> >>>use (multiface or digiface) which have differing channel counts.
> >>>So when we do get this working, it will be a problem to handle
> >>>both cases in a conf file.
> >>>
> >>
> >>Not to mention that there is also a shift in the S/PDIF channels
> >>position when the card changes speed mode...
> >>Can the current configuration mechanism handle this properly ?
> > 
> > 
> > when the channel position changes dynamically according to the certain
> > state, it'd be difficult with the current config without addition...
> >
> 
> In case you plan to implement those additions, let me know if there is 
> anything to adapt on the driver side.

sure.

anyway, we'll need to discuss the best way for this problem.
i'd like to avoid addition as much as possible.


Takashi


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-02-06 13:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 15:29 Questions to HDSP users Thomas Charbonnel
2004-01-28 19:22 ` Jesse Chappell
2004-01-29 13:51   ` Alsa handling of spdif bits (was Re: Questions to HDSP users) Thomas Charbonnel
2004-02-05 14:34     ` Takashi Iwai
2004-02-05 19:08       ` Jesse Chappell
2004-02-06 11:22         ` Thomas Charbonnel
2004-02-06 11:53           ` Takashi Iwai
2004-02-06 13:14             ` Thomas Charbonnel
2004-02-06 13:32               ` Takashi Iwai [this message]
2004-02-06 19:12                 ` Thomas Charbonnel
2004-02-09 10:52                   ` Takashi Iwai
2004-01-29 14:34 ` Questions to HDSP users Justin Cormack
2004-02-05  1:04 ` alsa-devel

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=s5h7jz08hak.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jesse@essej.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