All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Adam Goode <agoode@chromium.org>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Support for getting "manufacturer" from snd_seq_client_info and/or snd_ctl_card_info
Date: Fri, 16 May 2014 09:26:02 +0200	[thread overview]
Message-ID: <5375BD8A.2040201@ladisch.de> (raw)
In-Reply-To: <CAOf41N=cvQZv8ZaTKL6fhj98gywws0x+78CAYKuQJTh+YFBJ1w@mail.gmail.com>

Adam Goode wrote:
>> Clemens Ladisch wrote:
>>> 2. Add the manufacturer name to snd_ctl_card_info.  For USB devices,
>>>    this is almost always known, but most other drivers do not know the
>>>    name of the card manufacturer (as opposed to the chip manufacturer).
>>>    In those cases, the most informative name that a driver could provide
>>>    would be based on a registered ID like "USB:0x1234", "PCI:0x5678", or
>>>    "IEEE:0x9abcde".
>
> One question I have for step 2 above: snd_ctl_card_info is full. I
> don't see a way of adding to it without introducing a new ioctl
> (SNDRV_CTL_IOCTL_CARD_INFO2 + struct snd_ctl_card_info2?)

If you really want to avoid adding a new ioctl:  The numerical IDs are
just numbers, for which there is enough space in snd_ctl_card_info.  For
USB devices, the manufacturer name is part of the longname, so you'd
just need offset/length values.

And I'm not sure if it would be a good idea to expose the manufacturer
ID as a string.  Is that value supposed to be shown to the user, or just
some unique ID?


Regards,
Clemens

  parent reply	other threads:[~2014-05-16  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  1:18 Support for getting "manufacturer" from snd_seq_client_info and/or snd_ctl_card_info Adam Goode
2014-05-11  7:50 ` Clemens Ladisch
2014-05-12 19:29   ` Adam Goode
2014-05-13  9:24     ` Clemens Ladisch
2014-05-13 15:00       ` Takashi Iwai
2014-05-15 23:47         ` Adam Goode
2014-05-16  5:42           ` Takashi Iwai
2014-05-16  7:26           ` Clemens Ladisch [this message]
2014-05-21  3:23             ` Adam Goode

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=5375BD8A.2040201@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=agoode@chromium.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.