From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eliot Blennerhassett Subject: Re: Custom IOCTL call Date: Sat, 11 Dec 2010 12:23:40 +1300 Message-ID: <4D02B67C.10903@audioscience.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp5.clear.net.nz (smtp5.clear.net.nz [203.97.33.68]) by alsa0.perex.cz (Postfix) with ESMTP id 5EB7C10380C for ; Sat, 11 Dec 2010 00:23:47 +0100 (CET) Received: from [192.168.36.2] (121-72-250-62.cable.telstraclear.net [121.72.250.62]) by smtp5.clear.net.nz (CLEAR Net Mail) with ESMTP id <0LD800FPNJNJ4I10@smtp5.clear.net.nz> for alsa-devel@alsa-project.org; Sat, 11 Dec 2010 12:23:43 +1300 (NZDT) In-reply-to: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Radivoje Jovanovic Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On 11/12/10 08:42, Radivoje Jovanovic wrote: > I am writing custom IOCTL calls for my card. I have made hwdep interface and > set ioctl ops call for it. But, now the question is which device I need to > open in my user space app to talk to correct ioctl? /dev/snd/hwC0D0 > I have tried /dev/snd/controlC0 > and /dev/snd/pcmC0D0p