From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Prabhu Sundararaj <prabhu.sundararaj@nxp.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH v2 05/14] imx-gpu-viv: Upgrade to 6.2.2.p0
Date: Mon, 20 Nov 2017 09:26:05 -0200 [thread overview]
Message-ID: <CAP9ODKrk9qAH+cu0waUJKSn4Akr3aaqeaEu9wWBEXkrS1PnYPw@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0402MB29033DB051B791B135D12D1BE62F0@DB6PR0402MB2903.eurprd04.prod.outlook.com>
Hello Prabhu,
On Fri, Nov 17, 2017 at 8:37 PM, Prabhu Sundararaj
<prabhu.sundararaj@nxp.com> wrote:
> Hi Otavio, Gary,
> We tested only on SABRE boards and it got only 2GB MAX DDR.
Ok, this is a valid point but this does not mean it covers all
possible use-cases.
>> Using 4.1.15 of_reserved_mem.c works too but that is just a
>> workaround, the viv driver should manage that case since Etnaviv does.
> Wondering whether this restriction came in 4.9?
>
> This is not regression from in my point of view. May be we consider this a requirement and fix it in separate patch.
Sorry but it is a regression. The previous GA release works with 4GiB
of RAM. The new one does not.
> Fixing this and validation would require some time.
Gary did figure out the root cause. He found two important information pieces:
- A similar issue was seen and fixed on Etnaviv[1]. I guess a
similar patch is required for this driver as well. Forcing the cma
area to be under 0x90000000 (for imx6qdl) makes the driver work.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=471070ab
- A new patch[2], that is included in 4.9, changes the behavior of it
[2] https://github.com/boundarydevices/linux-imx6/commit/e53b50c0cbe392c946807abf7d07615a3c588642
Another important aspect is that the 6.2.3.p0[3] available for i.MX8
adds a new gc_hal_kernel_allocator_reserved_mem.c to address this very
issue.
[3] http://git.freescale.com/git/cgit.cgi/imx/linux-imx.git/commit/drivers/mxc/gpu-viv?id=fe649d5ca8e6088d54eee89825705257f404576d
So I think it all provides a good information about the issue. It
seems that backporting the gc_hal_kernel_allocator_reserved_mem.c is
the best option as it allows for no diverting of Linux kernel official
behavior.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2017-11-20 11:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 21:02 [PATCH v2 00/14] Graphics updates for L4.9.11-1.0.0 BSP Release plus Weston 2.0 Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 01/14] libdrm: Extend ARM support to mx7 Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 02/14] eglinfo-fb: Use generic header Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 03/14] imx-gpu-apitrace: Move apitrace out of imx-gpu-viv v6 Tom Hochstein
2017-11-16 15:52 ` Otavio Salvador
2017-11-15 21:02 ` [PATCH v2 04/14] imx-gpu-g2d: Move imx-gpu-g2d " Tom Hochstein
2017-11-22 2:53 ` S. Lockwood-Childs
2017-11-22 18:09 ` Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 05/14] imx-gpu-viv: Upgrade to 6.2.2.p0 Tom Hochstein
2017-11-16 11:37 ` Gary Bisson
2017-11-16 12:43 ` Otavio Salvador
2017-11-17 22:37 ` Prabhu Sundararaj
2017-11-20 11:26 ` Otavio Salvador [this message]
2017-11-15 21:02 ` [PATCH v2 06/14] imx-gpu-viv: Add systemd init Tom Hochstein
2017-11-16 15:50 ` Otavio Salvador
2017-11-15 21:02 ` [PATCH v2 07/14] mesa: Remove parts provided by imx-gpu-viv v6 Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 08/14] piglit: Remove redundant dependency Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 09/14] xserver-xf86-config: Add Xorg configuration for i.MX 6SLL and 7ULP Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 10/14] xf86-video-imxfb-vivante: Upgrade to 6.2.2.p0 Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 11/14] gtk+3: Use egl pkgconfig for build setup Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 12/14] weston: Switch to 2.0 with i.MX fork Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 13/14] weston-init: Fix weston 2.0 startup for pam, systemd case Tom Hochstein
2017-11-15 21:02 ` [PATCH v2 14/14] libepoxy: Fix build break for EGL_CAST dependency Tom Hochstein
2017-11-16 15:48 ` Otavio Salvador
2017-11-16 15:54 ` [PATCH v2 00/14] Graphics updates for L4.9.11-1.0.0 BSP Release plus Weston 2.0 Otavio Salvador
2017-11-16 16:26 ` Tom Hochstein
2017-11-16 16:36 ` Otavio Salvador
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=CAP9ODKrk9qAH+cu0waUJKSn4Akr3aaqeaEu9wWBEXkrS1PnYPw@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=meta-freescale@yoctoproject.org \
--cc=prabhu.sundararaj@nxp.com \
/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.