On Tue, Feb 11, 2014 at 11:00:48PM +0530, Vinod Koul wrote:
On Tue, Feb 04, 2014 at 02:42:35PM -0600, Andy Gross wrote:
Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA
controller
found in the MSM 8x74 platforms.
[.]
+ * QCOM BAM DMA engine driver
On Mon, Feb 10, 2014 at 06:55:02PM +0200, Ivan T. Ivanov wrote:
[]
Bail here?
I don't know. What will be the consequences if controller continue to
operate on its default rate?
It is unclear. But if you can't set the rate that is configured or if
there is
a
On Fri, Feb 07, 2014 at 11:52:33AM +0200, Ivan T. Ivanov wrote:
Hi Andy,
On Fri, 2014-02-07 at 01:39 -0600, Andy Gross wrote:
On Thu, Feb 06, 2014 at 06:57:48PM +0200, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Qualcomm Universal Peripheral (QUP) core
On Fri, Feb 07, 2014 at 05:52:34PM +, Mark Brown wrote:
On Fri, Feb 07, 2014 at 11:32:07AM -0600, Andy Gross wrote:
On Fri, Feb 07, 2014 at 11:52:33AM +0200, Ivan T. Ivanov wrote:
[... snip ...]
The platform doesn't have support for PM right now. So it's probably
better
On Thu, Feb 06, 2014 at 06:57:48PM +0200, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Qualcomm Universal Peripheral (QUP) core is an AHB slave that
provides a common data path (an output FIFO and an input FIFO)
for serial peripheral interface (SPI) mini-core. SPI in master
On Thu, Feb 06, 2014 at 06:57:47PM +0200, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
The Qualcomm Universal Peripheral (QUP) core is an
AHB slave that provides a common data path (an output
FIFO and an input FIFO) for serial peripheral interface
(SPI) mini-core.
On Tue, Feb 04, 2014 at 12:58:25PM +0100, Lars-Peter Clausen wrote:
On 02/04/2014 12:04 AM, Andy Gross wrote:
[...]
+static int bam_dma_remove(struct platform_device *pdev)
+{
+struct bam_device *bdev = platform_get_drvdata(pdev);
+u32 i;
+
+dma_async_device_unregister(bdev
of standard types.
Andy Gross (2):
dmaengine: add Qualcomm BAM dma driver
dmaengine: qcom_bam_dma: Add device tree binding
.../devicetree/bindings/dma/qcom_bam_dma.txt | 48 +
drivers/dma/Kconfig|9 +
drivers/dma/Makefile
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 48
1 file changed, 48 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma
the peripheral and system memory (System mode), or
between two peripherals (BAM2BAM).
The initial release of this driver only supports slave transfers between
peripherals and system memory.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
drivers/dma/Kconfig|9 +
drivers/dma/Makefile
.
- Renamed files to reflect vendor name instead of specific device
- Converted to use (readl|writel)_relaxed w/ appropriate barriers
- Removed unions in favor of standard types.
Andy Gross (2):
dmaengine: add Qualcomm BAM dma driver
dmaengine: qcom_bam_dma: Add device tree binding
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 48
1 file changed, 48 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma
the peripheral and system memory (System mode), or
between two peripherals (BAM2BAM).
The initial release of this driver only supports slave transfers between
peripherals and system memory.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
drivers/dma/Kconfig|9 +
drivers/dma/Makefile
On Fri, Jan 24, 2014 at 02:24:27PM +0100, Lars-Peter Clausen wrote:
On 01/24/2014 12:16 PM, Srikanth Thokala wrote:
Hi Lars,
On Thu, Jan 23, 2014 at 4:55 PM, Lars-Peter Clausen l...@metafoo.de wrote:
On 01/22/2014 05:52 PM, Srikanth Thokala wrote:
[...]
+/**
+ *
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
+
+Clients must use the format described in the dma.txt file, using a three
cell
+specifier for each channel.
+
+The three cells in order are:
+ 1. A
On Tue, Jan 28, 2014 at 10:05:35AM +0100, Lars-Peter Clausen wrote:
On 01/28/2014 07:27 AM, Andy Gross wrote:
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 52
file.
- Renamed files to reflect vendor name instead of specific device
- Converted to use (readl|writel)_relaxed w/ appropriate barriers
- Removed unions in favor of standard types.
Andy Gross (2):
dmaengine: add Qualcomm BAM dma driver
dmaengine: qcom_bam_dma: Add
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 52
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma
the peripheral and system memory (System mode), or
between two peripherals (BAM2BAM).
The initial release of this driver only supports slave transfers between
peripherals and system memory.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
drivers/dma/Kconfig|9 +
drivers/dma/Makefile
On Thu, Jan 23, 2014 at 02:17:19PM -0600, Kumar Gala wrote:
[]
Thanks for the clarification. I think I'll probably do:
ARCH_MSM_DT || (COMPILE_TEST ARM)
Didn?t you need it to be:
ARCH_MSM_DT || (COMPILE_TEST OF ARM)
- k
Yes. That's the version I am going with. I might
On Tue, Jan 21, 2014 at 09:03:43AM +0100, Arnd Bergmann wrote:
On Monday 20 January 2014 16:52:45 Andy Gross wrote:
+#ifdef CONFIG_OF
+static const struct of_device_id bam_of_match[] = {
+ { .compatible = qcom,bam-v1.4.0, },
+ { .compatible = qcom,bam-v1.4.1
On Fri, Jan 17, 2014 at 11:49:27PM +0100, Arnd Bergmann wrote:
On Friday 10 January 2014, Andy Gross wrote:
+static bool bam_dma_filter(struct dma_chan *chan, void *data)
+{
+ struct bam_filter_args *args = data;
+ struct bam_chan *bchan = to_bam_chan(chan);
+
+ if (args-dev
On Tue, Jan 14, 2014 at 11:43:48AM -0800, Stephen Boyd wrote:
(Mostly nitpicks)
On 01/10, Andy Gross wrote:
Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA
controller
found in the MSM 8x74 platforms.
Each BAM DMA device is associated with a specific on-chip
On Mon, Jan 13, 2014 at 10:31:01AM +, Shevchenko, Andriy wrote:
On Fri, 2014-01-10 at 13:07 -0600, Andy Gross wrote:
Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA
controller
found in the MSM 8x74 platforms.
Each BAM DMA device is associated with a specific
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 52 ++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma
the peripheral and system memory (System mode), or
between two peripherals (BAM2BAM).
The initial release of this driver only supports slave transfers between
peripherals and system memory.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
drivers/dma/Kconfig| 9 +
drivers/dma/Makefile
- Removed proprietary slave config. Removed associated include file.
- Renamed files to reflect vendor name instead of specific device
- Converted to use (readl|writel)_relaxed w/ appropriate barriers
- Removed unions in favor of standard types.
Andy Gross (2):
dmaengine: add
On Wed, Nov 13, 2013 at 06:48:12PM +0530, Vinod Koul wrote:
On Thu, Nov 07, 2013 at 05:03:17PM -0600, Andy Gross wrote:
On Thu, Oct 31, 2013 at 04:46:21PM -0500, Andy Gross wrote:
On Thu, Oct 31, 2013 at 10:29:48PM +0530, Vinod Koul wrote:
On Fri, Oct 25, 2013 at 03:24:02PM -0500, Andy
On Thu, Oct 31, 2013 at 04:46:21PM -0500, Andy Gross wrote:
On Thu, Oct 31, 2013 at 10:29:48PM +0530, Vinod Koul wrote:
On Fri, Oct 25, 2013 at 03:24:02PM -0500, Andy Gross wrote:
This should be sent to dmaeng...@vger.kernel.org
I'll add the list when I send the second iteration
On Thu, Oct 31, 2013 at 10:29:48PM +0530, Vinod Koul wrote:
On Fri, Oct 25, 2013 at 03:24:02PM -0500, Andy Gross wrote:
This should be sent to dmaeng...@vger.kernel.org
I'll add the list when I send the second iteration or should I send it over mid
stream?
Add the DMA engine driver
On Tue, Oct 29, 2013 at 10:56:03AM -0700, Stephen Boyd wrote:
On 10/25, Andy Gross wrote:
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index f238cfd..a71b415 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -364,4 +364,13 @@ config DMATEST
Simple DMA test
will only support slave DMA operations
between system memory and peripherals.
Andy Gross (2):
dmaengine: add msm bam dma driver
dmaengine: msm_bam_dma: Add device tree binding
.../devicetree/bindings/dma/msm_bam_dma.txt| 49 ++
drivers/dma/Kconfig
the peripheral and system memory (System mode) or
between two peripherals (BAM2BAM).
The initial release of this driver only supports slave transfers between
peripherals and system memory.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
drivers/dma/Kconfig|9 +
drivers/dma/Makefile
201 - 233 of 233 matches
Mail list logo
