2010/5/2 Russell King - ARM Linux :
>> But the implementation of the DMA engine would be better of
>> handling the muxing dynamically I believe, so when the PL011
>> driver (say) requests a DMA channel, it doesn't mean it requests the
>> *physical* channel and holds it (unless the driver is very n
2010/5/2 Dan Williams :
> On Sat, May 1, 2010 at 4:04 PM, Linus Walleij
>> When the driver issues a request to perform a DMA transfer, it will pull
>> out a physical channel and use that, then return it. If there is too
>> much combat about the physical channels, you configure out DMA
>> for the l
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 Sun, May 02, 2010 at 01:04:37AM +0200, 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
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
>> somewhere to allow any inco
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 for (eg) AACI
> or MMC.
As long as Versatile doesn't specify
> I explicitly confirmed this on top of 2.6.33.2:
Thanks that makes a bit more sense.
>
> config-2.6.33.2.git19f00f0-config-2.6.33-2-amd64.nohiber:CONFIG_MEMORY_HOTPLUG=y
> =>"bad"
> config-2.6.33.2.git19f00f0-config-2.6.33-2-amd64.nohotplug:#
> CONFIG_MEMORY_HOTPLUG is not set
> =>"good"
>
>
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
> somewhere to allow any incompatibilities to be worked out later
> in-tree?
What I don't want to
2010/5/2 Dan Williams :
> On Thu, Apr 22, 2010 at 4:00 AM, Russell King - ARM Linux
> wrote:
>> So has this (which has now been applied to Dan's tree) been tested
>> as I asked on Versatile platforms, or do we have something that could
>> be incompatible with those platforms?
>>
>> I'm basically n
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 great!
>>
>> > The other patch in -mm I could take
On Fri, 2010-04-30 at 19:06 +0200, Andi Kleen wrote:
> The mission information is which CONFIG_* option changes the behaviour.
> (or maybe it's in the bugzilla, i just skimmed it very quickly)
>
> presumably it's either hibernation or memory hotadd that introduces
> the problem.
>
> My patch just
11 matches
Mail list logo
