All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: dma_alloc_coherent fails in framebuffer
Date: Sun, 14 Oct 2012 18:28:43 +1300	[thread overview]
Message-ID: <1350192523.10946.4.camel@gitbox> (raw)

Up until 07 Oct, drivers/video/wm8505-fb.c was working fine, but on the
11 Oct when I did another pull from linus all of a sudden
dma_alloc_coherent is failing to allocate the framebuffer any longer.

I did a quick look back and found this:

ARM: add coherent dma ops

arch_is_coherent is problematic as it is a global symbol. This
doesn't work for multi-platform kernels or platforms which can support
per device coherent DMA.

This adds arm_coherent_dma_ops to be used for devices which connected
coherently (i.e. to the ACP port on Cortex-A9 or A15). The arm_dma_ops
are modified at boot when arch_is_coherent is true.

Signed-off-by: Rob Herring <rob.herring@calxeda.com>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>


This is the only patch lately that I could find (not that I would claim
to be any good at finding things) that is related to the problem. Could
it have caused the allocations to fail?

Regards
Tony P

             reply	other threads:[~2012-10-14  5:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14  5:28 Tony Prisk [this message]
2012-10-14 20:34 ` dma_alloc_coherent fails in framebuffer Tony Prisk
2012-10-14 20:34   ` Tony Prisk
2012-10-14 22:26   ` Tony Prisk
2012-10-14 22:26     ` Tony Prisk
2012-10-15  6:42     ` Tomasz Figa
2012-10-15  6:42       ` Tomasz Figa
2012-10-15  8:03       ` Tony Prisk
2012-10-15  8:03         ` Tony Prisk
2012-10-15 13:35         ` Marek Szyprowski
2012-10-15 13:35           ` Marek Szyprowski
2012-10-15  9:45   ` Mel Gorman
2012-10-15  9:45     ` Mel Gorman
2012-10-15 18:28     ` Tony Prisk
2012-10-15 18:28       ` Tony Prisk
2012-10-16  2:17       ` Bob Liu
2012-10-16  2:17         ` Bob Liu
2012-10-16  5:02         ` Tony Prisk
2012-10-16  5:54         ` Tony Prisk
2012-10-16  5:54           ` Tony Prisk
2012-10-16  6:50           ` Tony Prisk
2012-10-16  6:50             ` Tony Prisk
2012-10-16  7:58             ` Mel Gorman
2012-10-16  7:58               ` Mel Gorman
2012-10-16  8:13               ` Tony Prisk
2012-10-16  8:13                 ` Tony Prisk
2012-10-16 14:41         ` James Bottomley
2012-10-16 14:41           ` James Bottomley
2012-10-17  2:26           ` Bob Liu
2012-10-17  2:26             ` Bob Liu

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=1350192523.10946.4.camel@gitbox \
    --to=linux@prisktech.co.nz \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.