public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts sunxi: Relax a bit the CMA pool allocation range
Date: Mon, 6 Jul 2020 15:11:05 +0200	[thread overview]
Message-ID: <20200706131105.vfjfka2fxsi3i3ua@gilmour.lan> (raw)
In-Reply-To: <CAGb2v66mY-vd05akkcGFHVQm_BUfmuTYkw05V6wyiTbCz6Vd_g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1329 bytes --]

On Mon, Jul 06, 2020 at 11:18:51AM +0800, Chen-Yu Tsai wrote:
> On Sat, Jul 4, 2020 at 9:08 PM Maxime Ripard <maxime@cerno.tech> wrote:
> >
> > The hardware codec on the A10, A10s, A13 and A20 needs buffer in the
> > first 256MB of RAM. This was solved by setting the CMA pool at a fixed
> > address in that range.
> >
> > However, in recent kernels there's something else that comes in and
> > reserve some range that end up conflicting with our default pool
> > requirement, and thus makes its reservation fail.
> >
> > The video codec will then use buffers from the usual default pool,
> > outside of the range it can access, and will fail to decode anything.
> >
> > Since we're only concerned about that 256MB, we can however relax the
> > allocation to just specify the range that's allowed, and not try to
> > enforce a specific address.
> >
> > Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
> > Fixes: 5949bc5602cc ("ARM: dts: sun4i-a10: Add Video Engine and reserved memory nodes")
> > Fixes: 960432010156 ("ARM: dts: sun5i: Add Video Engine and reserved memory nodes")
> > Fixes: c2a641a74850 ("ARM: dts: sun7i-a20: Add Video Engine and reserved memory nodes")
> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> 
> Acked-by: Chen-Yu Tsai <wens@csie.org>

Applied, thanks!
Maxime

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-07-06 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-04 13:08 [PATCH] ARM: dts sunxi: Relax a bit the CMA pool allocation range Maxime Ripard
2020-07-06  3:18 ` Chen-Yu Tsai
2020-07-06 13:11   ` Maxime Ripard [this message]

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=20200706131105.vfjfka2fxsi3i3ua@gilmour.lan \
    --to=maxime@cerno.tech \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=wens@csie.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