From: Fabrice Gasnier <fabrice.gasnier@st.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <alexandre.torgue@st.com>, <thierry.reding@gmail.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 v4 2/6] mfd: stm32-timers: add support for dmas
Date: Tue, 17 Apr 2018 09:37:59 +0200 [thread overview]
Message-ID: <34e30463-6236-a8e4-fd1f-6217612375eb@st.com> (raw)
In-Reply-To: <20180417071250.yhgl7c7apn7w53xf@dell>
On 04/17/2018 09:12 AM, Lee Jones wrote:
> On Mon, 16 Apr 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 <fabrice.gasnier@st.com>
>> Reviewed-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>
>> ---
>> Changes in v4:
>> - Lee's comments: Add kerneldoc header, better format comments.
>> 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 | 227 ++++++++++++++++++++++++++++++++++++++-
>> include/linux/mfd/stm32-timers.h | 32 ++++++
>> 2 files changed, 257 insertions(+), 2 deletions(-)
>
> [...]
>
>> diff --git a/include/linux/mfd/stm32-timers.h b/include/linux/mfd/stm32-timers.h
>> index 2aadab6..a04d7a1 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 <linux/clk.h>
>> +#include <linux/dmaengine.h>
>> +#include <linux/dma-mapping.h>
>> #include <linux/regmap.h>
>
> [...]
>
>> +struct stm32_timers_dma;
>> +
>> struct stm32_timers {
>> struct clk *clk;
>> struct regmap *regmap;
>> u32 max_arr;
>> + struct stm32_timers_dma *dma; /* Only to be used by the parent */
>
> I'm confused. I thought the point of putting this comment in was so
> that you could place the definition of 'stm32_timers_dma' and remove
> the forward declaration?
Hi Lee,
Sorry, if I miss-understood the point then. So, do you wish I both:
- move the full struct definition in above header ?
- and keep this comment ?
+/**
+ * struct stm32_timers_dma - STM32 timer DMA handling.
+ * @completion: end of DMA transfer completion
+ * @phys_base: control registers physical base address
+ * @lock: protect DMA access
+ * @chan: DMA channel in use
+ * @chans: DMA channels available for this timer instance
+ */
+struct stm32_timers_dma {
+ struct completion completion;
+ phys_addr_t phys_base;
+ struct mutex lock;
+ struct dma_chan *chan;
+ struct dma_chan *chans[STM32_TIMERS_MAX_DMAS];
+};
This will basically expose the struct to child drivers. But I'm ok if
you think this is acceptable.
I can send a V5 if you wish...
Please advise,
Best regards,
Fabrice
>
>> };
>> +
>> +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
>
next prev parent reply other threads:[~2018-04-17 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 16:19 [PATCH v4 0/6] Add support for PWM input capture on STM32 Fabrice Gasnier
2018-04-16 16:19 ` [PATCH v4 1/6] dt-bindings: mfd: stm32-timers: add support for dmas Fabrice Gasnier
2018-04-16 16:19 ` [PATCH v4 2/6] " Fabrice Gasnier
2018-04-17 7:12 ` Lee Jones
2018-04-17 7:37 ` Fabrice Gasnier [this message]
2018-04-17 10:10 ` Lee Jones
2018-04-17 11:54 ` Fabrice Gasnier
2018-04-17 11:25 ` Dan Carpenter
2018-04-16 16:19 ` [PATCH v4 3/6] pwm: stm32: add capture support Fabrice Gasnier
2018-04-16 16:19 ` [PATCH v4 4/6] pwm: stm32: improve capture by tuning counter prescaler Fabrice Gasnier
2018-04-16 16:19 ` [PATCH v4 5/6] pwm: stm32: use input prescaler to improve period capture Fabrice Gasnier
2018-04-16 16:19 ` [PATCH v4 6/6] ARM: dts: stm32: Enable pwm3 input capture on stm32f429i-eval Fabrice Gasnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34e30463-6236-a8e4-fd1f-6217612375eb@st.com \
--to=fabrice.gasnier@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®