From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: RFC: minimalistic TLV implementation Date: Thu, 01 Jun 2006 17:18:09 +0200 Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (ns2.suse.de [195.135.220.15]) by alsa.jcu.cz (ALSA's E-mail Delivery System) with ESMTP id 43E8F15A for ; Thu, 1 Jun 2006 17:18:18 +0200 (MEST) Received: from Relay1.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id 067F41CC39 for ; Thu, 1 Jun 2006 17:18:09 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@lists.sourceforge.net Errors-To: alsa-devel-bounces@lists.sourceforge.net To: Jaroslav Kysela Cc: ALSA development List-Id: alsa-devel@alsa-project.org At Thu, 1 Jun 2006 17:16:13 +0200 (CEST), Jaroslav Kysela wrote: > > On Thu, 1 Jun 2006, Takashi Iwai wrote: > > > Well, but this ioctl is damn simple. Just query a control element for > > its TLV data. > > > > It's supposed to be the one containing all. If we need a filter of > > returned data, the query header should contain a type field rather > > than flags. > > Sure, but this ioctl can handle global data (not numid dependant) as well. > If we decide to have two ioctls then it's also ok to me. Yeah, I prefer two ioctls now, too. (But we don't need to add the global ioctl yet unless we really need it...) Takashi