From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: "Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Clément Péron" <peron.clem@gmail.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
linux-sunxi@lists.linux.dev,
linux-kernel <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH v1] ARM: dts: sun8i: h3: orangepi-pc: Add CMA reserved memory node
Date: Wed, 14 Sep 2022 20:34:49 +0200 [thread overview]
Message-ID: <1826631.tdWV9SEqCh@jernej-laptop> (raw)
In-Reply-To: <CAJiuCcefkre611=1UXEkwScN+bYSBhE_ivGzTK7ZMvp-j4MbRQ@mail.gmail.com>
Dne sreda, 14. september 2022 ob 17:33:27 CEST je Clément Péron napisal(a):
> Hi Dmitry,
>
> On Wed, 14 Sept 2022 at 17:12, Dmitry Osipenko
>
> <dmitry.osipenko@collabora.com> wrote:
> > Add 256MB CMA node to the Orange Pi PC board. This fixes memory allocation
> > failures for Cedrus video decoder on trying to play a 1080p video with
> > gstreamer.
> >
> > Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > ---
> >
> > arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts
> > b/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts index
> > b96e015f54ee..e655346a9fb4 100644
> > --- a/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts
> > +++ b/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts
> > @@ -60,6 +60,20 @@ chosen {
> >
> > stdout-path = "serial0:115200n8";
> >
> > };
> >
> > + reserved-memory {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + ranges;
> > +
> > + linux,cma@40000000 {
> > + compatible = "shared-dma-pool";
> > + alloc-ranges = <0x40000000 0x40000000>;
> > + size = <0x10000000>; /* 256MiB */
> > + linux,cma-default;
> > + reusable;
> > + };
> > + };
> > +
>
> This change seems legit for all H3 boards and could be moved to the H3 dtsi,
> no?
That's true. However, there is a reason why this node doesn't exist. One or
two H2+ boards (which use H3 dtsi) have only 256 MiB of RAM, so this can't
work with them. A few H3 boards have 512 MiB of RAM, so you eat basically half
of the RAM with that. Additionally, contrary to A20 and similar SoCs, which
have such node, Cedrus can address whole RAM, so this is not strictly needed.
It's better to leave this decision to distribution. Some don't care about
Cedrus and some do a lot. Default size can be set via kernel config and it can
be overriden by kernel argument if necessary.
Best regards,
Jernej
>
> Regards,
> Clement
>
> > connector {
> >
> > compatible = "hdmi-connector";
> > type = "a";
> >
> > --
> > 2.37.3
next prev parent reply other threads:[~2022-09-14 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 15:11 [PATCH v1] ARM: dts: sun8i: h3: orangepi-pc: Add CMA reserved memory node Dmitry Osipenko
2022-09-14 15:33 ` Clément Péron
2022-09-14 18:34 ` Jernej Škrabec [this message]
2022-09-15 9:01 ` Dmitry Osipenko
2022-10-12 22:17 ` Jernej Škrabec
2022-10-13 13:36 ` Dmitry Osipenko
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=1826631.tdWV9SEqCh@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=peron.clem@gmail.com \
--cc=samuel@sholland.org \
--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