All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Jörn Nettingsmeier" <nettings@stackingdwarves.net>
Cc: Adrian Knoth <adi@drcomp.erfurt.thur.de>, alsa-devel@alsa-project.org
Subject: Re: hdspm.c - confused about	SNDRV_HDSPM_IOCTL_GET_[CONFIG|STATUS]
Date: Wed, 18 May 2011 18:17:37 +0200	[thread overview]
Message-ID: <s5h7h9o2db2.wl%tiwai@suse.de> (raw)
In-Reply-To: <4DCFFFF3.4000502@stackingdwarves.net>

At Sun, 15 May 2011 18:31:47 +0200,
Jörn Nettingsmeier wrote:
> 
> hi *!
> 
> 
> i'm trying to extend hdspconf to work with the rme hdspm madi card, and 
> got confused over the snd_hdspm_hwdep_ioctl:
> 
> apparently, the hdspm.c driver differentiates between settable controls 
> (CONFIG) and non-settable status indicators (STATUS), unlike the earlier 
> hdspm.c.
> 
> however, usage seems a bit inconsistent:
> 
> struct hdspm_config contains a member madi_sync_check, which is 
> apparently never set.

This was also in the older version, and the structure wasn't changed
for compatibility reason.

> instead, struct hdspm_status card_specific.sync_madi is used, same for 
> tco and sync in.
> 
> but there is a wordclock_sync_check in struct hdspm_config which is in use.
> 
> am i guessing right that the latter is somewhat deprecated and that i 
> should be taking all status values from struct hdspm_status instead?

Well, consider GET_STATUS as a kind of extended attributes.


Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2011-05-18 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 16:31 hdspm.c - confused about SNDRV_HDSPM_IOCTL_GET_[CONFIG|STATUS] Jörn Nettingsmeier
2011-05-18 16:17 ` Takashi Iwai [this message]

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=s5h7h9o2db2.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=adi@drcomp.erfurt.thur.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=nettings@stackingdwarves.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.