From: Clemens Ladisch <clemens@ladisch.de>
To: Ivan Bublikov <ivanbublikov@yahoo.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Hardware-specific IOCTLs
Date: Fri, 13 Jan 2012 18:31:18 +0100 [thread overview]
Message-ID: <4F106A66.4080803@ladisch.de> (raw)
In-Reply-To: <1326471758.45923.YahooMailNeo@web121806.mail.ne1.yahoo.com>
Ivan Bublikov wrote:
> As an HDA codec vendor, I want to be able to control some functionality
> in my codec, that is not present in codecs from other vendors. [...]
> I can register an IOCTL handler using snd_ctl_register_ioctl.
This functions is for ioctl calls on the ctl device, which is global
for one sound card and is not appropriate if one wants to address
something like a PCM device or a codec.
For a HDA codec, use a hwdep device.
> My difficulty is how to define a code for my IOCTL and avoid
> a conflict with the common code in the future.
Pick something not yet allocated in Documentation/ioctl/ioctl-number.txt.
Regards,
Clemens
next prev parent reply other threads:[~2012-01-13 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 16:22 Hardware-specific IOCTLs Ivan Bublikov
2012-01-13 17:31 ` Clemens Ladisch [this message]
2012-01-13 22:45 ` Ivan Bublikov
2012-01-17 22:02 ` Clemens Ladisch
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=4F106A66.4080803@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=ivanbublikov@yahoo.com \
/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.