Received: by 2002:a05:6358:700f:b0:131:369:b2a3 with SMTP id 15csp995291rwo; Wed, 2 Aug 2023 07:17:31 -0700 (PDT) X-Google-Smtp-Source: APBJJlHsJURR5D8CrRR2FsUuj9OFRbexK003G7a/JNa+7449YY/Gg0B3CXJvgjY+xu7I8c0IOsYu X-Received: by 2002:a05:6a20:1586:b0:139:8517:10b6 with SMTP id h6-20020a056a20158600b00139851710b6mr18089249pzj.30.1690985850731; Wed, 02 Aug 2023 07:17:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690985850; cv=none; d=google.com; s=arc-20160816; b=rNHvCM60EQWZYO/BQVtOqqFSIzKY7avAjU2xwUOk9nJ31AuNRyCS4tLgH3hancXpFN i731ZC4frm8wiTBIu8H4BJchH+/rIL7hEP5R8b5geAteZs0vrh3RhOfJ7FFP/3LWAaba 1MAcGEjSYnSe4DUFXX4piekVdZRkHRkaXluv2dCH4eply+hoCqygiDA8M7UDvLOlF6tG IpJm60QRJZw5of0tZWLWk2fVmEIkwq2/eByvdE83U/yiEwlCzPH5Ra11RYD6bfh7Bk2r MSq2dHX3vTSyeWYSpzYHlkKAftM64X3uz8tnoJhImr1NJj0TPatSsasd6eK5QiI+b4n8 Nc8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:subject:cc:to:from:message-id :date:dkim-signature:dkim-signature; bh=wxPHjo3+ia+QJjBrjbeie8E5g2hZQ55e92AAzrGOhEI=; fh=vlySLsrOslQJt7hxzjOCsM267oDArcuzwF7wi0UR3+M=; b=JELE022zRW2gelmYLz+Qf7YNoiAu74Ec6L6lY02dkhPzaZif8eEbmYpsmWnhMRhECg eziOqQtn46VUlcS+BEPml2kPc9W6oAi6sOXx2dY7OQ0XlY71N+jqwIatFDcoKkKQFbcm 6nRwrH8vmGJNjSbMQxhkgTvSlddO4cINerRSwIB71OPTyurldzk2lreOV0F1m+G9Hfc2 N01h05aKkO2aXXNu43w44KBwSEcky+yr1Zqfk0Z41TQRnm0OGfJUunmngbiJ3iSYLF/o muwgTfqrjRuV584Hsj4VHKtb4QDS0YwS75B0sKCwFMXs9ddPkkUKcbuuv10QxyqIUKNm 6unA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=AXjMJDzt; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z33-20020a056a001da100b006870878c6dbsi1924483pfw.191.2023.08.02.07.17.16; Wed, 02 Aug 2023 07:17:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=AXjMJDzt; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234338AbjHBMIj (ORCPT + 99 others); Wed, 2 Aug 2023 08:08:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42958 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231974AbjHBMIi (ORCPT ); Wed, 2 Aug 2023 08:08:38 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F1851BFD; Wed, 2 Aug 2023 05:08:37 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 122E81F38D; Wed, 2 Aug 2023 12:08:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1690978116; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wxPHjo3+ia+QJjBrjbeie8E5g2hZQ55e92AAzrGOhEI=; b=AXjMJDzt8LQ5Aws+NBUjfUEoMB9Yz7f6O0HMW0it0ifUd7WEIaIHEP4qncTGjhhD6EDoxb F7gnLl+5o8NiHW19hpC3ep6emXodiyGqOw2WhbgfiVBTf4qGBKd7jTJ1qGRp85rauiY6Oa d1aiZV+hUmtFcwdfyiPu5SoMzIcBsZw= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1690978116; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wxPHjo3+ia+QJjBrjbeie8E5g2hZQ55e92AAzrGOhEI=; b=a5+VLwV3cvmphzmj2zlwrNKt4nmwdNbp2bySub5cb7YvNuOmBZ5b0GmUbqi8u7jfqmS9X0 to8kobwjwCyaFLAg== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id DB90A13909; Wed, 2 Aug 2023 12:08:35 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id WG4jNUNHymR8PwAAMHmgww (envelope-from ); Wed, 02 Aug 2023 12:08:35 +0000 Date: Wed, 02 Aug 2023 14:08:35 +0200 Message-ID: <87il9xoddo.wl-tiwai@suse.de> From: Takashi Iwai To: Shengjiu Wang Cc: Hans Verkuil , Shengjiu Wang , sakari.ailus@iki.fi, tfiga@chromium.org, m.szyprowski@samsung.com, mchehab@kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, Xiubo.Lee@gmail.com, festevam@gmail.com, nicoleotsuka@gmail.com, lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [RFC PATCH v2 0/7] Add audio support in v4l2 framework In-Reply-To: References: <1690265540-25999-1-git-send-email-shengjiu.wang@nxp.com> <47d66c28-1eb2-07f5-d6f9-779d675aefe8@xs4all.nl> <87il9xu1ro.wl-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 02 Aug 2023 14:02:29 +0200, Shengjiu Wang wrote: > > On Wed, Aug 2, 2023 at 7:22 PM Takashi Iwai wrote: > > > > On Wed, 02 Aug 2023 09:32:37 +0200, > > Hans Verkuil wrote: > > > > > > Hi all, > > > > > > On 25/07/2023 08:12, Shengjiu Wang wrote: > > > > Audio signal processing has the requirement for memory to > > > > memory similar as Video. > > > > > > > > This patch is to add this support in v4l2 framework, defined > > > > new buffer type V4L2_BUF_TYPE_AUDIO_CAPTURE and > > > > V4L2_BUF_TYPE_AUDIO_OUTPUT, defined new format v4l2_audio_format > > > > for audio case usage. > > > > > > > > The created audio device is named "/dev/audioX". > > > > > > > > And add memory to memory support for two kinds of i.MX ASRC > > > > module > > > > > > Before I spend time on this: are the audio maintainers OK with doing > > > this in V4L2? > > > > > > I do want to have a clear statement on this as it is not something I > > > can decide. > > > > Well, I personally don't mind to have some audio capability in v4l2 > > layer. But, the only uncertain thing for now is whether this is a > > must-have or not. > > > > Thanks, I am also not sure about this. I am also confused that why > there is no m2m implementation for audio in the kernel. Audio also > has similar decoder encoder post-processing as video. > > > > > IIRC, the implementation in the sound driver side was never done just > > because there was no similar implementation? If so, and if the > > extension to the v4l2 core layer is needed, shouldn't it be more > > considered for the possible other route? > > > > Actually I'd like someone could point me to the other route. I'd like to > try. > > The reason why I select to extend v4l2 for such audio usage is that v4l2 > looks best for this audio m2m implementation. v4l2 is designed for m2m > usage. if we need implement another 'route', I don't think it can do better > that v4l2. > > I appreciate that someone can share his ideas or doable solutions. > And please don't ignore my request, ignore my patch. Can you explain a bit more details of your demand? At least, a "big picture" showing how your hardware is implemented and what is exactly necessary would be helpful for understanding the problem. thanks, Takashi