On Thu, Oct 18, 2012 at 7:51 PM, Matt Porter wrote:
> Add a dmaengine API to retrieve per channel capabilities.
> Currently, only channel ops and SG segment limitations are
> implemented caps.
>
> The API is optionally implemented by drivers and when
> unimplemented will return a NULL pointer. It
On Wed, Jun 8, 2011 at 1:41 PM, Russell King - ARM Linux
wrote:
> On Wed, Jun 08, 2011 at 01:05:57PM -0700, Dan Williams wrote:
>> Even if that were the case it would be same situation that the scsi device
>> driver reports maximum parameters, but the subsystem opts for
>&
On Wed, Jun 8, 2011 at 12:10 AM, FUJITA Tomonori
wrote:
> On Tue, 7 Jun 2011 23:56:21 -0700
> Dan Williams wrote:
>
>> > The dma parameter restriction could be due to software (HBA drivers,
>> > or subsystem). The value should be whatever the dma device driver s
On Tue, Jun 7, 2011 at 10:23 PM, FUJITA Tomonori
wrote:
> On Mon, 6 Jun 2011 11:48:56 -0700
> Dan Williams wrote:
>
>> dmaengine expands the class of dma providers to include standalone dma
>> agents on a host bus (or elsewhere) in addition to the traditional bus
>>
On Mon, Jun 6, 2011 at 12:30 AM, Shawn Guo wrote:
> Like dma_set(get)_max_seg_size for max_segment_size, the patch adds
> max_segment_number into device_dma_parameters and creates the
> corresponding dmaengine API dma_set(get)_max_seg_number for it.
>
> Here is the user story that tells the need o
On Mon, Jun 6, 2011 at 3:12 AM, FUJITA Tomonori
wrote:
> On Mon, 6 Jun 2011 10:47:51 +0100
> Russell King - ARM Linux wrote:
>
>> On Mon, Jun 06, 2011 at 06:41:09PM +0900, FUJITA Tomonori wrote:
>> > On Mon, 6 Jun 2011 10:14:10 +0100
>> > Russell King - ARM Linux wrote:
>> >
>> > > On Mon, Jun 0
ring the IRQ handler later and
> making it capable of handling interrupts with no cause. The change that
> makes the IRQ handler registration happen later actually eliminates
> the spurious interrupt as well.
>
> Signed-off-by: Daniel Drake
Acked-by: Dan Williams
> ---
&
On Sun, Jun 20, 2010 at 9:40 PM, Paul Mundt wrote:
> On Mon, Jun 07, 2010 at 01:16:36PM +0200, Guennadi Liakhovetski wrote:
>> To use DMA engine based DMA with MMC in a non-modular build, the DMA
>> engine has to initialise before MMC.
>>
>> Signed-off-by: Guennadi Liakhovetski
>
> Dan, any objec
On Wed, May 12, 2010 at 12:39 AM, Linus WALLEIJ
wrote:
> [Dan]
>
>> >> +void dma_set_ambaconfig(struct dma_chan *chan,
>> >> + struct amba_dma_channel_config *config)
>> >
>> > What happens when two primecell dma devices are present on one soc?
>> > Can that happen? In that
On Tue, May 11, 2010 at 9:37 AM, Dan Williams wrote:
> On Sun, May 2, 2010 at 5:54 PM, Linus Walleij
> wrote:
>> This extends the DMA engine driver for the COH 901 318 used in the
>> U300 platform with the generic PrimeCell interface.
>>
>> Signed-off-by: Linus W
On Sun, May 2, 2010 at 5:54 PM, Linus Walleij
wrote:
> This extends the DMA engine driver for the COH 901 318 used in the
> U300 platform with the generic PrimeCell interface.
>
> Signed-off-by: Linus Walleij
> ---
> drivers/dma/coh901318.c | 146
> +
On Sun, May 9, 2010 at 3:06 AM, jassi brar wrote:
> This discussion is purely about what the current DMA API misses and what
> a generic DMA API should do. So, that the current DMA API fills up those
> gap, if possible. I would love to get started implementing the generic
> DMA API for reference b
On Sat, May 8, 2010 at 8:48 PM, jassi brar wrote:
> On Sun, May 9, 2010 at 7:24 AM, Dan Williams wrote:
>> On Fri, May 7, 2010 at 7:37 PM, jassi brar wrote:
>>> IMHO, a DMA api should be as quick as possible - callbacks done in IRQ
>>> context.
>>> But si
On Fri, May 7, 2010 at 7:37 PM, jassi brar wrote:
> On Sat, May 8, 2010 at 1:10 AM, Linus Walleij
> wrote:
>> Surely circular linked buffers and other goodies can be retrofitted into the
>> DMAengine without a complete redesign? I only see a new slave call
>> to support that really, in addition t
On Fri, May 7, 2010 at 4:43 AM, Linus Walleij
wrote:
> 2010/5/7 Russell King - ARM Linux :
>
>> I would have thought given the concerns that I stated, merely running
>> the drivers in PIO mode would not address those concerns. So no, I'm
>> not satisfied.
>
> Sorry didn't get it, I understood it
On Sat, May 1, 2010 at 4:04 PM, Linus Walleij
wrote:
> 2010/5/2 Russell King - ARM Linux :
>
>> Versatile has some MUXing on three of the DMA signals, so (eg) we
>> really don't want UARTs claiming DMAs just because they're in existence
>> and not in use - that would prevent DMAs from being used f
On Sat, May 1, 2010 at 3:44 PM, Russell King - ARM Linux
wrote:
> On Sat, May 01, 2010 at 03:00:09PM -0700, Dan Williams wrote:
>> Just to clarify are you nak'ing these patches for upstream inclusion
>> until this testing occurs? Or do we just need a !ARCH_VERSATILE
>&
On Thu, Apr 22, 2010 at 4:00 AM, Russell King - ARM Linux
wrote:
> On Sat, Apr 17, 2010 at 06:58:49AM +0200, Linus Walleij wrote:
>> 2010/4/15 Dan Williams :
>>
>> > Getting closer... I have pushed out the dma40 driver (v3), 4, and 6.
>>
>> That's grea
Hi Linus,
On Wed, Apr 7, 2010 at 11:35 PM, Linus WALLEIJ
wrote:
> If it's OK with Russell, putting 04-06 plus 09 through async_tx
> tree is a good starter.
Getting closer... I have pushed out the dma40 driver (v3), 4, and 6.
The other patch in -mm I could take as well but that needs an ack from
Hi Linus,
On Wed, Apr 7, 2010 at 4:12 PM, Linus Walleij
wrote:
> This extends the DMA engine driver for the COH 901 318 used in the
> U300 platform with the generic PrimeCell interface.
>
> Signed-off-by: Linus Walleij
> ---
> drivers/dma/coh901318.c | 146
> ++
Hi Linus, back online now.
On Wed, Apr 7, 2010 at 4:12 PM, Linus Walleij
wrote:
> This is the fifth iteration of this ever growing patch set
> for PrimeCell DMA support, reposting the entire series.
>
> This now depend on stuff pending in Dan Williams async_tx
> (DMA Devices/E
right direction.
>
> Signed-off-by: Daniel Mack
> Cc: Alagu Sankar
> Cc: Volker Ernst
> Cc: Dan Williams
> Cc: John W. Linville
> Cc: Holger Schurig
> Cc: Bing Zhao
> Cc: libertas-...@lists.infradead.org
> Cc: linux-wirel...@vger.kernel.org
> Cc: l
if_sdio_probe() does.
Thanks!
Dan
> Signed-off-by: Daniel Mack
> Cc: Alagu Sankar
> Cc: Volker Ernst
> Cc: Dan Williams
> Cc: John W. Linville
> Cc: Holger Schurig
> Cc: Bing Zhao
> Cc: libertas-...@lists.infradead.org
> Cc: linux-wirel...@vger.kernel.org
> Cc:
o be at least somewhat SPI related?
Acked-by: Dan Williams
> Thanks to Alagu Sankar for pointing me in the right direction.
>
> Signed-off-by: Daniel Mack
> Cc: Alagu Sankar
> Cc: Volker Ernst
> Cc: Dan Williams
> Cc: John W. Linville
> Cc: Holger Schurig
> Cc: Bing Z
On Thu, 2009-10-29 at 11:27 +0100, Daniel Mack wrote:
> On Wed, Oct 28, 2009 at 10:06:02AM -0700, Dan Williams wrote:
> > On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > > I did some more research on this and it turns out that the problem is
> > > related t
On Wed, 2009-10-28 at 18:19 +0100, Daniel Mack wrote:
> On Wed, Oct 28, 2009 at 10:06:02AM -0700, Dan Williams wrote:
> > On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > > I did some more research on this and it turns out that the problem is
> > > related t
On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> > On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > > Hi,
> > >
> > > we're having trouble getting SDIO connected harwa
On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> > On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > > Hi,
> > >
> > > we're having trouble getting SDIO connected harwa
On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> Hi,
>
> we're having trouble getting SDIO connected harware to fly on MX31 based
> designs. In particular, a SD8686 chip supported by the libertas_sdio
> driver will hang forever when built without CONFIG_MMC_DEBUG=y. With
> that option selec
29 matches
Mail list logo
