Received: by 10.192.165.156 with SMTP id m28csp592041imm; Mon, 16 Apr 2018 05:44:51 -0700 (PDT) X-Google-Smtp-Source: AIpwx49oxYXYA3RKRYGjunqZd3HQWJHIKoeXn42x5TTocNuCZdiZP4pqAdr8+OT2tBO9OXMqaOiO X-Received: by 10.98.33.72 with SMTP id h69mr8598854pfh.54.1523882691909; Mon, 16 Apr 2018 05:44:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523882691; cv=none; d=google.com; s=arc-20160816; b=KeDW56TolJ0rBprMWyHPZUJgUQxze7Kxyy3rZcm6cJUsr/VHwjgqi1iqqLSamfG6kK XXvOlQOdvJU6JwLUB4TMZDtihX1biarjAuxKVRrK+aV/4IrggP+xg/4oW7mPCmU7oaj9 b4POaq6hf+Y6IcZPAhpLti/Si0CzXU3cHsc84pgXzbVJoavjlF28gZhzkUC49k5Xh8hd KcQZvqdydZhdD9miaW6DPNg6DVcjwQ9AbsPrnxtkun8pH8h76OykMHsIyEr5ENaVcp8D sNddL4RVhuPAtqLvR/dsUmlOouEsvLKQuUKnOYFBZdhR+R7Fi6JZ11sP0X6rgsfhdpve ZoYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=/vQUOwKHz03n/K31Y3AG08UibARCjLjOb7xDfMSFmE4=; b=NDkXufdi8x41/llgmQdvQNz1ursuwbnmHcULul/uIzlcY7ExXkukNivR7USZv7AyE7 0u0ORmoBeD+eUmZ3majham4Uq1zgFvWM9bNpDQ1FO3u6KvO5Bj7ypgh9fBM2h2xcxS9s yWVW1uNA3vmyls+d7vkkD/sANbtpudzituSr402T4WIDBmN1yMsCedQegj/yvySevW+P KL7vZ+RGOm1fw8MwytB4jXGDfxCKon7qwUIMgo8zCtj4WsJpTIm7D52VSZPllXNNGcEU b8BthrcEcuSHklXPqBiuw+42U0eYX2WdM8dKn2wT2JYgcIN9/D9G9hHhMn1dEcWSy0aQ 20LQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=bCfnNd8U; 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 x9-v6si12073050pln.508.2018.04.16.05.44.07; Mon, 16 Apr 2018 05: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=bCfnNd8U; 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 S1753084AbeDPMWY (ORCPT + 99 others); Mon, 16 Apr 2018 08:22:24 -0400 Received: from mail-wr0-f195.google.com ([209.85.128.195]:46612 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752593AbeDPMWV (ORCPT ); Mon, 16 Apr 2018 08:22:21 -0400 Received: by mail-wr0-f195.google.com with SMTP id d1so25410073wrj.13 for ; Mon, 16 Apr 2018 05:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=/vQUOwKHz03n/K31Y3AG08UibARCjLjOb7xDfMSFmE4=; b=bCfnNd8UXBLdowx3lI/MlkMNrplFKw+hn6z86vrmhS6K5GeNSlDWPoVp2ZajwAMxqQ h+ZKG1caxxI6tx4JTRy8Ibgb2M0zE7/NdDDGw5OGxCQzJrPm+zlSi7HcLlWg15NH4r1z C/F12yZehijq0tbZIwQOropOS9SdQNB/dc01g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=/vQUOwKHz03n/K31Y3AG08UibARCjLjOb7xDfMSFmE4=; b=m07ciehQ/JICc37AETixQmzNPQBx0JxnDJU8Q4kBYsUE7WziEg24so8/VcAo2HM2mZ mTq1wtcAgRGllREt937dq11otf9nyp7MTI/Tl/32UHAB7G39IqvhlXT8t8eRG4Fj28RF am1YXsifW4f/5SXyUwr66OSWFR2NyzY6GlO2zw/tURx9A5pBWGgRclT0welkL0jPwheQ ytKA1C8DzpyYYM1p1MTmN5RBetXJ51rkLNkI+TMLLg8okB+/dgv02dvM/QBM0SGZyFHO GZ0EsRrDGZAJPWblL9g7yM0OxeJFxUXllqamY38/uOIdTV/eDdSyi1GbtraMeBCod6OY LbVQ== X-Gm-Message-State: ALQs6tD54CXt/x31xG9oc0ITnC3m9OxDNW7JVAseEEaDLj0uacn9A+5f 4IPlrhwD2QT4k8fuSON5jX2N0g== X-Received: by 10.28.111.16 with SMTP id k16mr9491496wmc.35.1523881340288; Mon, 16 Apr 2018 05:22:20 -0700 (PDT) Received: from dell ([2.27.167.70]) by smtp.gmail.com with ESMTPSA id b13sm8707710wmi.42.2018.04.16.05.22.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 16 Apr 2018 05:22:19 -0700 (PDT) Date: Mon, 16 Apr 2018 13:22:17 +0100 From: Lee Jones To: Fabrice Gasnier Cc: thierry.reding@gmail.com, alexandre.torgue@st.com, benjamin.gaignard@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk, mcoquelin.stm32@gmail.com, benjamin.gaignard@st.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org Subject: Re: [PATCH v3 2/6] mfd: stm32-timers: add support for dmas Message-ID: <20180416122217.u7h3wawpdx3kj4wd@dell> References: <1522404084-24903-1-git-send-email-fabrice.gasnier@st.com> <1522404084-24903-3-git-send-email-fabrice.gasnier@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1522404084-24903-3-git-send-email-fabrice.gasnier@st.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 30 Mar 2018, Fabrice Gasnier wrote: > STM32 Timers can support up to 7 DMA requests: > - 4 channels, update, compare and trigger. > Optionally request part, or all DMAs from stm32-timers MFD core. > > Also add routine to implement burst reads using DMA from timer registers. > This is exported. So, it can be used by child drivers, PWM capture > for instance (but not limited to). > > Signed-off-by: Fabrice Gasnier > Reviewed-by: Benjamin Gaignard > --- > Changes in v3: > - Basically Lee's comments: > - rather create a struct stm32_timers_dma, and place a reference to it > in existing ddata (instead of adding priv struct). > - rather use a struct device in exported routine prototype, and use > standard helpers instead of ddata. Get rid of to_stm32_timers_priv(). > - simplify error handling in probe (remove a goto) > - comment on devm_of_platform_*populate() usage. > > Changes in v2: > - Abstract DMA handling from child driver: move it to MFD core > - Add comments on optional dma support > --- > drivers/mfd/stm32-timers.c | 219 ++++++++++++++++++++++++++++++++++++++- > include/linux/mfd/stm32-timers.h | 32 ++++++ > 2 files changed, 249 insertions(+), 2 deletions(-) > > diff --git a/drivers/mfd/stm32-timers.c b/drivers/mfd/stm32-timers.c > index 1d347e5..98191ec 100644 > --- a/drivers/mfd/stm32-timers.c > +++ b/drivers/mfd/stm32-timers.c > @@ -4,16 +4,165 @@ > * Author: Benjamin Gaignard > */ > > +#include > +#include > +#include > #include > #include > #include > #include > > +#define STM32_TIMERS_MAX_REGISTERS 0x3fc > + > +struct stm32_timers_dma { > + struct completion completion; > + phys_addr_t phys_base; > + struct mutex lock; /* protect dma access */ Nit: I like comments to use good grammar i.e. capital letters to start a sentence and 's/dma/DMA/'. Or better still, drop the comment, we know what the lock is for. > + struct dma_chan *chan; > + struct dma_chan *chans[STM32_TIMERS_MAX_DMAS]; This requires explanation. Maybe a kerneldoc header would be good here. [...] > +/** > + * stm32_timers_dma_burst_read - Read from timers registers using DMA. > + * > + * Read from STM32 timers registers using DMA on a single event. > + * @dev: reference to stm32_timers MFD device > + * @buf: dma'able destination buffer > + * @id: stm32_timers_dmas event identifier (ch[1..4], up, trig or com) > + * @reg: registers start offset for DMA to read from (like CCRx for capture) > + * @num_reg: number of registers to read upon each dma request, starting @reg. > + * @bursts: number of bursts to read (e.g. like two for pwm period capture) > + * @tmo_ms: timeout (milliseconds) > + */ > +int stm32_timers_dma_burst_read(struct device *dev, u32 *buf, > + enum stm32_timers_dmas id, u32 reg, > + unsigned int num_reg, unsigned int bursts, > + unsigned long tmo_ms) > +{ > + struct stm32_timers *ddata = dev_get_drvdata(dev); > + unsigned long timeout = msecs_to_jiffies(tmo_ms); > + struct regmap *regmap = ddata->regmap; > + struct stm32_timers_dma *dma = ddata->dma; > + size_t len = num_reg * bursts * sizeof(u32); > + struct dma_async_tx_descriptor *desc; > + struct dma_slave_config config; > + dma_cookie_t cookie; > + dma_addr_t dma_buf; > + u32 dbl, dba; > + long err; > + int ret; > + > + /* sanity check */ Proper grammar in all comments please. "Sanity check" [...] > + /* select dma channel in use */ Here too. Etc, etc, etc ... > + dma->chan = dma->chans[id]; > + dma_buf = dma_map_single(dev, buf, len, DMA_FROM_DEVICE); > + ret = dma_mapping_error(dev, dma_buf); > + if (ret) > + goto unlock; > + > + /* Prepare DMA read from timer registers, using DMA burst mode */ This is good. [...] [...] > diff --git a/include/linux/mfd/stm32-timers.h b/include/linux/mfd/stm32-timers.h > index 2aadab6..585a4de 100644 > --- a/include/linux/mfd/stm32-timers.h > +++ b/include/linux/mfd/stm32-timers.h > @@ -8,6 +8,8 @@ > #define _LINUX_STM32_GPTIMER_H_ > > #include > +#include > +#include > #include [...] > +enum stm32_timers_dmas { > + STM32_TIMERS_DMA_CH1, > + STM32_TIMERS_DMA_CH2, > + STM32_TIMERS_DMA_CH3, > + STM32_TIMERS_DMA_CH4, > + STM32_TIMERS_DMA_UP, > + STM32_TIMERS_DMA_TRIG, > + STM32_TIMERS_DMA_COM, > + STM32_TIMERS_MAX_DMAS, > +}; > + > +struct stm32_timers_dma; Why don't you move the declaration into here? Then you don't need to forward declare. > struct stm32_timers { > struct clk *clk; > struct regmap *regmap; > u32 max_arr; > + struct stm32_timers_dma *dma; > }; > + > +int stm32_timers_dma_burst_read(struct device *dev, u32 *buf, > + enum stm32_timers_dmas id, u32 reg, > + unsigned int num_reg, unsigned int bursts, > + unsigned long tmo_ms); > #endif -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog