Received: by 10.192.165.156 with SMTP id m28csp348638imm; Thu, 12 Apr 2018 23:44:52 -0700 (PDT) X-Google-Smtp-Source: AIpwx48PyYiI0ak1FVkTvhqsNehWOQI+YMsW5cecsVVgXEoyMp3E9ywgTaXUhWWzDG8Id+REDduk X-Received: by 2002:a17:902:a50d:: with SMTP id s13-v6mr4062879plq.228.1523601891965; Thu, 12 Apr 2018 23:44:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523601891; cv=none; d=google.com; s=arc-20160816; b=nqgJXEdwc28vS7nEYnZcFQ9SZA0hUSxEcd8fgB3ox4gnhirDjudUn6QIALS7vG9S5A xswWOgXMB0S3uew1p8q4JIk2FdQk4bM5pOd8KEwCv1nKDWVBX4+ByXCzbi8j/3Zk9V7O mgU1tlZZ2jPW1S/ofrHrWZ3IJJLzvt5VasfFKRAlY8r/FBiDn/CK8JCF3mwjt45XKPsG x8QeTeR9oOiQy3zDOb8tPjjPg4A+w2HmyPp/bS1PqjRhy7Qx/69LTIQhEp+JtD6fHWYM Ms0gPf1rCHEsrSTmUEjz1zfTcv2EycGxAX18QwfEfFXgdI2KCHD25G5kassEP+Lfksb3 ORUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=H5NZthmJAtHfhBGkEGNTCx7N62OAwPXesxs5p668b/c=; b=jVLkcXW072Q0/LsjGyKQyja3DkxBdSyhPNTH4MwYPvK9COxPWd5j8WbqmgVZbTntLX XKwyFD3zriERfx4alVfiaqjCviLKrGOtN13qn7PxnFgvvF41ZBEnOCg9zI0WjrwFRL1L mo026WPwV2eGSqtf5O4Q2x60zS1kS4XltwmMg2qtIoDxG/3m10P+dRc0M1V5rcHsm0c3 PJIs0qFfWO2McwyqAy/7YqrBhimLniwh0Wzxd0CnUF0MPjYjvV47FlbaSh4EKGsa9g2O gCBFXOvhdik1tECC+e/DMzA2sU4KxAhpEJg3iCVJfItU8F6jgSxX+51SD6yYzCdDvCCF nElQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=PIKiNPYC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 2-v6si5130065pla.436.2018.04.12.23.44.38; Thu, 12 Apr 2018 23:44:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=PIKiNPYC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753468AbeDMGlv (ORCPT + 99 others); Fri, 13 Apr 2018 02:41:51 -0400 Received: from mail-ot0-f169.google.com ([74.125.82.169]:36955 "EHLO mail-ot0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752594AbeDMGlt (ORCPT ); Fri, 13 Apr 2018 02:41:49 -0400 Received: by mail-ot0-f169.google.com with SMTP id y46-v6so8760671otd.4 for ; Thu, 12 Apr 2018 23:41:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=H5NZthmJAtHfhBGkEGNTCx7N62OAwPXesxs5p668b/c=; b=PIKiNPYCQvxtuhdz6NMr222eENqqsWok7A/ufQNu6/P+hHG+yFX65+hkiCNGJm7+lh sInMZaUktpytNVTHYpKWS7vo6y7Rfeezfe6BcoxZdQHhJ1QpZPCI6d0E5VDOa6N5EeqA 8b8R8CAxcFHnpf1TzPj05Mq7nsm1iKO9TTHWg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=H5NZthmJAtHfhBGkEGNTCx7N62OAwPXesxs5p668b/c=; b=oJtxCJha3Gka3vHF+LM4jQdpmKhrFOGNofXkWJh6a8aDw1MQLxvdzt0YPW8Ia0OUpK j2Sd+HvTlnI8NRqITaTu0wAk+SUZHKQrFJXKcr3qYmiqC12Qlx34C3r87p3ndr0Lz7Hs hts/5zwlQGOuNtG7qb0FKy6Kzjsyvhsrc7unpUo4pyuBA3Z3r/bGbjQDsTvmnpXKtrRD JU6nfWQTPFKRTqFLTsMJ1Dm8LPyMqGnNK2W8jsEBiIweWmjJCs1p13NHw4fUeyIjzBD7 4TqAyWfFlPamlIGpZR6+pB6Pubwk7U5sQhInhwLvNKjjJK9fXwWY78RRSxkaxrahDXc9 9/HQ== X-Gm-Message-State: ALQs6tATwzfaDOF/DVn68h7JvcHtam/Um9rg2JIIFa404haGRphTg8+k /cx1svWL2rgoQTu5T/bBl+ZHdvYE2XDBQKoby4u14nG3 X-Received: by 2002:a9d:624d:: with SMTP id i13-v6mr2872588otk.26.1523601708915; Thu, 12 Apr 2018 23:41:48 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:7081:0:0:0:0:0 with HTTP; Thu, 12 Apr 2018 23:41:48 -0700 (PDT) In-Reply-To: <20180413063641.GL6014@localhost> References: <0c2b76aba6a49e583f920ae582d6815fa9cc4361.1523346135.git.baolin.wang@linaro.org> <20180411093634.GC6014@localhost> <20180412093735.GF6014@localhost> <20180413034332.GI6014@localhost> <20180413063641.GL6014@localhost> From: Baolin Wang Date: Fri, 13 Apr 2018 14:41:48 +0800 Message-ID: Subject: Re: [PATCH 4/5] dmaengine: sprd: Add Spreadtrum DMA configuration To: Vinod Koul Cc: Dan Williams , Eric Long , Mark Brown , dmaengine@vger.kernel.org, LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13 April 2018 at 14:36, Vinod Koul wrote: > On Fri, Apr 13, 2018 at 02:17:34PM +0800, Baolin Wang wrote: > >> > Agreed, users only care about grabbing a channel, setting a descriptor and >> > submitting that. >> > >> > I think you need to go back and think about this a bit, please do go thru >> > dmaengine documentation and see other driver examples. >> > >> > We don't typically expose these to users, they give us a transfer and we set >> > that up in hardware for efficient. Its DMA so people expect us to use fastest >> > mechanism available. >> >> But there are some configuration are really special for Spreadtrum >> DMA, and must need user to specify how to configure, especially some >> scenarios of audio. So I wander if we can add one pointer for >> 'dma_slave_config' to expand some special DMA configuration >> requirements, like: >> >> struct dma_slave_config { >> ...... >> unsigned int slave_id; >> void *platform_data; >> }; >> >> So if some DMA has some special configuration (such as Spreadtrum >> DMA), they can user this platform_data pointer. Like xilinx DMA, they >> also have some special configuration. > > Well we all think our HW is special and needs some additional stuff, most of > the cases turns out not to be the case. > > Can you explain how audio in this case additional configuration... > Beside the general configuration, our audio driver will configure the fragment length, block length, maybe transaction length, and they must specify the request type and interrupt type, these are what we want to export for users. -- Baolin.wang Best Regards