From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2540C2D0C0 for ; Mon, 23 Dec 2019 15:05:04 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4206E20409 for ; Mon, 23 Dec 2019 15:05:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="vnglzbBr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4206E20409 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 064D81691; Mon, 23 Dec 2019 16:04:11 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 064D81691 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1577113501; bh=T/ON6Q+gOSpDEIyaOQ9LBrpxhVCNFWiAWia5b+2Lvmc=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=vnglzbBr1l3B50DHzA1RmW9RLFE7jkZCfqgpE5UGlEv7QcsAf+4UxOxkG2DGP0GMC OO2XKS8ro7a6uQO/D6UPIxYg/iIdx/1mtUZRxAbB7+mC8fT1oKCrpx59cnCPIMmLzh cJxUYo7hITuXHlgD9QdlVc4s/rIsjHdANWPEnIt8= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 9F33CF800AD; Mon, 23 Dec 2019 16:03:58 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id AE05FF80146; Mon, 23 Dec 2019 16:03:56 +0100 (CET) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 13693F80132 for ; Mon, 23 Dec 2019 16:03:54 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 13693F80132 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id ACA33ADE4; Mon, 23 Dec 2019 15:03:53 +0000 (UTC) Date: Mon, 23 Dec 2019 16:03:53 +0100 Message-ID: From: Takashi Iwai To: Takashi Sakamoto In-Reply-To: <20191223093347.15279-1-o-takashi@sakamocchi.jp> References: <20191223093347.15279-1-o-takashi@sakamocchi.jp> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Cc: alsa-devel@alsa-project.org Subject: Re: [alsa-devel] [PATCH] ALSA: ctl: allow TLV read operation for callback type of element in locked case X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, 23 Dec 2019 10:33:47 +0100, Takashi Sakamoto wrote: > > A design of ALSA control core allows applications to execute three > operations for TLV feature; read, write and command. Furthermore, it > allows driver developers to process the operations by two ways; allocated > array or callback function. In the former, read operation is just allowed, > thus developers uses the latter when device driver supports variety of > models or the target model is expected to dynamically change information > stored in TLV container. > > The core also allows applications to lock any element so that the other > applications can't perform write operation to the element for element > value and TLV information. When the element is locked, write and command > operation for TLV information are prohibited as well as element value. > Any read operation should be allowed in the case. > > At present, when an element has callback function for TLV information, > TLV read operation returns EPERM if the element is locked. On the > other hand, the read operation is success when an element has allocated > array for TLV information. In both cases, read operation is success for > element value expectedly. > > This commit fixes the bug. This change can be backported to v4.14 > kernel or later. The patch looks good but your sign-off is missing... thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel