linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Orion5x: Fix too small coherent pool.
Date: Tue, 25 Sep 2012 01:16:10 +0200	[thread overview]
Message-ID: <5060E9BA.7010806@gmail.com> (raw)
In-Reply-To: <20120924173739.GG14266@lunn.ch>

On 09/24/2012 07:37 PM, Andrew Lunn wrote:
> On Mon, Sep 24, 2012 at 12:37:16PM -0400, Jason Cooper wrote:
>> On Mon, Sep 24, 2012 at 07:54:33AM +0200, Andrew Lunn wrote:
>>> Some Orion5x devices allocate their coherent buffers from atomic
>>> context. Increase size of atomic coherent pool to make sure such the
>>> allocations won't fail during boot.
>>>
>>> Signed-off-by: Andrew Lunn<andrew@lunn.ch>
>>
>> Acked-by: Jason Cooper<jason@lakedaemon.net>
>>
>> btw - we should take this to it's logical conclusion and have Sebastian
>> check Dove.  Sebastian?
>
> I did think about that. It probably hits if you have two sata
> devices. However, all current Dove machines have just one.

Jason, Andrew,

I did boot arm-soc/for-next on Cubox and looks like 256k pool for atomic
coherent allocations is enough. I booted with sata, sdhci0, eth0, i2c0,
spi0, and both pcie ports forced on without any pcie devices attached.

Sebastian

  reply	other threads:[~2012-09-24 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24  5:54 [PATCH] ARM: Orion5x: Fix too small coherent pool Andrew Lunn
2012-09-24 16:37 ` Jason Cooper
2012-09-24 17:37   ` Andrew Lunn
2012-09-24 23:16     ` Sebastian Hesselbarth [this message]
2012-09-24 23:45       ` Jason Cooper
2012-09-24 23:47         ` Olof Johansson
2012-09-25  0:04           ` Jason Cooper

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=5060E9BA.7010806@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).