From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: defconfig: Increase CMA size for VC4
Date: Thu, 03 May 2018 14:20:42 -0700 [thread overview]
Message-ID: <87bmdwo2qd.fsf@anholt.net> (raw)
In-Reply-To: <1525296700-3588-1-git-send-email-stefan.wahren@i2se.com>
Stefan Wahren <stefan.wahren@i2se.com> writes:
> The VC4 needs more memory than the default setting (16 MB):
>
> vc4-drm soc:gpu: swiotlb: coherent allocation failed, size=16777216
> [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
> vc4_v3d 3fc00000.v3d: Failed to allocate memory for tile binning: -12.
> You may need to enable CMA or give it more memory.
> vc4-drm soc:gpu: failed to bind 3fc00000.v3d (ops vc4_v3d_ops [vc4]): -12
> vc4-drm soc:gpu: master bind failed: -12
> vc4-drm: probe of soc:gpu failed with error -12
>
> So increase the value to 32 MB and fix this issue.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
If there was a way to check how big the CMA pool is, then we could
probably have V3D disable itself when the pool was too small. It's not
like V3D rendering is going to actually *work* with just a 32mb pool to
play in.
That said, I'd also be fine with this patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180503/04dd6dce/attachment.sig>
next prev parent reply other threads:[~2018-05-03 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 21:31 [PATCH] arm64: defconfig: Increase CMA size for VC4 Stefan Wahren
2018-05-03 21:20 ` Eric Anholt [this message]
2018-05-12 9:10 ` Stefan Wahren
2018-05-12 17:36 ` Florian Fainelli
2018-05-13 16:58 ` Florian Fainelli
2018-05-13 19:10 ` Stefan Wahren
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=87bmdwo2qd.fsf@anholt.net \
--to=eric@anholt.net \
--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.