On Thu, Feb 25, 2010 at 12:39 PM, Steven J. Magnani
wrote:
> fsl_dma_update_completed_cookie() appears to calculate the last completed
> cookie incorrectly in the corner case where DMA on cookie 1 is in progress
> just following a cookie wrap.
>
> Signed-off-by: Steven J. Magnani
> ---
> diff -up
At some stage, Grant wrote:
> > First off, I did a tiny amount of research, and I didn't find any
> > existing OpenFirmware bindings for describing video displays.
> > Otherwise, I'd suggest considering that.
There's a binding for framebuffers but it sucks big time :-) It doesn't
provide a reliab
I agree device tree is the right direction to go.
Sent from my Android phone
- Original Message -
From:"Anatolij Gustschin"
To:"linuxppc-...@ozlabs.org"
Cc:"grant.lik...@secretlab.ca" ,
"linux-fb...@vger.kernel.org" ,
"york...@freescale.com" , "d...@denx.de" ,
"w...@denx.de" , "jri...
This patch fix the PHY poller, which can block the whole system. On a
Freescale PPC 834x this result in a delay of 450 us due the slow
communication with the PHY chip.
For PHY chips without interrupts, the status of the ethernet will be
polled every 2 sec. The poll function will read some register
Russell King - ARM Linux wrote:
> On Sun, Feb 28, 2010 at 03:07:57PM +0100, Albert Herranz wrote:
>> This patch makes part of the ARM dmabounce code available to other
>> architectures as a generic API.
>
> There is already a generic dma bounce implementation - it's called
> swiotlb - lib/swiotlb.
On Sun, Feb 28, 2010 at 1:44 AM, Mitch Bradley wrote:
> Grant Likely Wrote:
>> On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin wrote:
>> Also, since you're now in the realm of describing a video display,
>> which is separate from the display controller, you should consider
>> describing the d
On Sun, Feb 28, 2010 at 03:07:57PM +0100, Albert Herranz wrote:
> This patch makes part of the ARM dmabounce code available to other
> architectures as a generic API.
There is already a generic dma bounce implementation - it's called
swiotlb - lib/swiotlb.c. We should eventually switch the ARM
dm
Add support for the USB Enhanced Host Controller Interface included
in the "Hollywood" chipset of the Nintendo Wii video game console.
Signed-off-by: Albert Herranz
---
arch/powerpc/platforms/embedded6xx/Kconfig |1 +
drivers/usb/host/Kconfig |8 +
drivers/usb/host/ehci
The HCD_NO_COHERENT_MEM USB host controller driver flag can be enabled
to instruct the USB stack to avoid allocating coherent memory for USB
buffers.
This flag is useful to overcome some esoteric memory access restrictions
found in some platforms.
For example, the Nintendo Wii video game console i
Some of the devices in the "Hollywood" chipset of the Nintendo Wii video
game console have restrictions performing DMA transfers to the first
contiguous RAM region (known as MEM1).
For example, up to 3 bytes of the last word of a DMA transfer of a
non-32 bit aligned length to MEM1 may be lost.
Such
Add support for the PowerPC architecture for using the generic dmabounce
support on a per-device basis.
Signed-off-by: Albert Herranz
---
arch/powerpc/include/asm/device.h |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/include/asm/device.h
b/arch/powerpc
Update ARM dmabounce to use the generic dmabounce support.
Signed-off-by: Albert Herranz
---
arch/arm/Kconfig |4 +-
arch/arm/common/Kconfig |6 +-
arch/arm/common/dmabounce.c | 376 +++-
arch/arm/include/asm/device.h |2 +-
i
This patch makes part of the ARM dmabounce code available to other
architectures as a generic API.
See included kernel-doc annotations for the actual API implemented.
An architecture can opt-in for generic dmabounce support by defining
HAVE_DMABOUNCE.
This support will be used later to address DM
The coherent per-device memory handling functions use the in-kernel
bitmap library to account for the allocated regions.
The bitmap functions, though, do not protect the bitmap structure from
being modified concurrently. This can lead, for example, to double
allocations if dma_alloc_from_coherent(
Let the Nintendo Wii gaming console use per-device dma coherent allocations.
This will be used later by some of its drivers.
Signed-off-by: Albert Herranz
---
arch/powerpc/platforms/embedded6xx/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/platform
The following patch series adds USB 2.0 support for the Wii PowerPC
platform via the EHCI controller present in the "Hollywood" chipset
of the video game console.
v1 -> v2
- enable per-device DMA coherent support on the Wii
- add a generic dmabounce based on ARM dmabounce
- make PowerPC and ARM us
Use the generic per-device dma coherent allocator on powerpc.
This allows a driver to declare coherent memory area from where
a device can allocate coherent memory chunks.
Signed-off-by: Albert Herranz
---
arch/powerpc/include/asm/dma-mapping.h |1 +
arch/powerpc/kernel/dma.c |
Replace open-coded rate limiting logic with __ratelimit().
Signed-off-by: Akinobu Mita
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: linuxppc-...@ozlabs.org
---
arch/powerpc/platforms/iseries/pci.c | 10 +++---
1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/arch/power
Hi Anatolij,
[added cc: to devicetree-disc...@lists.ozlabs.org]
On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin wrote:
> Framebuffer drivers may want to get panel timing info
> from the device tree. This patch adds appropriate support.
> Subsequent patch for FSL DIU frame buffer driver
19 matches
Mail list logo
