Message ID | 20221101023521.2384586-1-yung-chuan.liao@linux.intel.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:6687:0:0:0:0:0 with SMTP id l7csp2681202wru; Mon, 31 Oct 2022 19:33:42 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4UOm95JmPVqOZDhK1ZybICv0DH3WekEOHFEglc7g8Rfd0ag5AeAdrUHHHQGx+BS2X0D3Wc X-Received: by 2002:a17:907:2705:b0:7ad:8460:7d30 with SMTP id w5-20020a170907270500b007ad84607d30mr15590943ejk.693.1667270022346; Mon, 31 Oct 2022 19:33:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667270022; cv=none; d=google.com; s=arc-20160816; b=Cs4CVB2qBrf9DBrkMMeIgiyOTDAkaGSzF3tvfijesL/UEv0TPkR1ARChlIKQK/9gff FwCZ+pj56PwGj3XIhsAEg8nWpp2EdFGo3UINZzqq8HAdToURC8uOUOd8WEL41a5Bt8Ii ECrfkmtNXQTp0X5DAshu7Myxhf2QXVmA612aYTl+5c7tN2FEVp2mNVZCOufNKNyPSirw PtrYZDXg7HKPbBJ28IR53ZUocrj4O28ruxP/aiQTYTHvLBVfe5QddBJ+T/YQ4Qe1cAKD u3plRHhsVvTLpVEaYD1MnaDPE4mD2HNFHxwFp/FZhVzP4418xr/iLt/FThWXvqcX9lud HL8w== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=Nln6Wa2G2gD7O0ckCnZZHZDXE/p5A5kS0JQzkgRnu+U=; b=CNEhDOXc9AVYWcuTRJPfJr/JGa8hClUHjjzWQjyxBuLFE8k+T3VGpZg2EsLfPfNNHN qjgeaiQBzEH6dsTESdKKxgr2vXQfe3bp6MK5os2xh6f94KdTkK0cq2bnKej7YVQLgw9T LQS05d9/7iNo3w74g3+H1AtWhg1XXhn83R8spjvGgoNPO/lyrk6KIdsyy6x8ZlFgKe1m 5UwSw/FeTFx0550R+rlm94AVm47V/UBqlK7CTlL8uVoeAuky1JpNUTjlSoTbml+1Bbk1 4KqAC5RpKb88aSED0Lg3cxt6kBVP/Q0dVSAjvTnsiCOSjBt6HKQfkEFj5fNwoNTY/JfC wKoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=cCT9HeB3; 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=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id dr22-20020a170907721600b007a11c253eaasi9805445ejc.809.2022.10.31.19.33.17; Mon, 31 Oct 2022 19:33:42 -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=@intel.com header.s=Intel header.b=cCT9HeB3; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229649AbiKACah (ORCPT <rfc822;kartikey406@gmail.com> + 99 others); Mon, 31 Oct 2022 22:30:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35706 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229468AbiKACaf (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 31 Oct 2022 22:30:35 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2AA8BCD5 for <linux-kernel@vger.kernel.org>; Mon, 31 Oct 2022 19:30:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667269835; x=1698805835; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=+VAcDu8nCS7WGVWXp6e7tdbtl+zUVq+Vu+cNVOMl7/0=; b=cCT9HeB3S10H8dWsnUZ14l6wvP2ZLmFRqld5tnLH9ZKjOpv1Z7nuPSOe FURIHu2SZ0Mo97oe16GP3TWzyGvYCuYcI0AYZKkWvNyyxLtyp12AxOrey xTwKbgtShbYHTeeqmm8L79/cyRol8m8/qV8dBIsWt7GdH4kq9gl8kO7WV asRLievFJi1zpMUg9voDt4WQ3zDjqMBmBx48iLyuAS/vBSSwc2opSoGeq +/bvdaP/aDFnyaGm55mXKHsz68IVSt3hYtBrdePGP3uBtT2q5JRa/XEo3 fxVSAxVq4uNF/9CbyOLxIzFBdXwVOBd+pebOmC54HUSjhhk4zMes6Xp3t g==; X-IronPort-AV: E=McAfee;i="6500,9779,10517"; a="288763719" X-IronPort-AV: E=Sophos;i="5.95,229,1661842800"; d="scan'208";a="288763719" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Oct 2022 19:30:34 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10517"; a="611709363" X-IronPort-AV: E=Sophos;i="5.95,229,1661842800"; d="scan'208";a="611709363" Received: from bard-ubuntu.sh.intel.com ([10.239.185.57]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Oct 2022 19:30:32 -0700 From: Bard Liao <yung-chuan.liao@linux.intel.com> To: alsa-devel@alsa-project.org, vkoul@kernel.org Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org, pierre-louis.bossart@linux.intel.com, bard.liao@intel.com Subject: [PATCH 0/2] soundwire: cadence: remove dma_data Date: Tue, 1 Nov 2022 10:35:19 +0800 Message-Id: <20221101023521.2384586-1-yung-chuan.liao@linux.intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_PASS, SPF_NONE 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1748259330820178827?= X-GMAIL-MSGID: =?utf-8?q?1748259330820178827?= |
Series |
soundwire: cadence: remove dma_data
|
|
Message
Bard Liao
Nov. 1, 2022, 2:35 a.m. UTC
The use of dma_data is problematic for two reasons for the Cadence IP. a) the dai runtime data has nothing to do with DMAs in existing solutions b) we will use the dma_data for DMA-management in the future. We cannot share two separate pieces of information with the same dma_data pointer. Pierre-Louis Bossart (2): soundwire: cadence: rename sdw_cdns_dai_dma_data as sdw_cdns_dai_runtime soundwire: cadence: use dai_runtime_array instead of dma_data drivers/soundwire/cadence_master.c | 50 +++++++------ drivers/soundwire/cadence_master.h | 9 ++- drivers/soundwire/intel.c | 111 ++++++++++++++--------------- 3 files changed, 86 insertions(+), 84 deletions(-)
Comments
On 01-11-22, 10:35, Bard Liao wrote: > The use of dma_data is problematic for two reasons for the Cadence IP. > a) the dai runtime data has nothing to do with DMAs in existing solutions > b) we will use the dma_data for DMA-management in the future. We cannot > share two separate pieces of information with the same dma_data pointer. Applied, thanks