lkml.org 
[lkml]   [2019]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Lay common foundation to make PVR/SGX work without hacks on OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5
From
Date
Hi Adam,

> Am 17.08.2019 um 01:01 schrieb Adam Ford <aford173@gmail.com>:
>
>
> Nikolaus,
>
> I tested Tony's change and I can confirm that I can read the value
> when enabled. Should I apply his patches to your branch before I
> test, or is it go too to go as-is?

My branch is currently as-is and not aware of Tony's patches and based on v5.3-rc3.
I think I will have to remove some glue code which tries to do the platform
reset and enables clocks and replace by pm_runtime_get_sync() before it fits
together. Then we can likely remove the omap-pvr-soc-glue branch at least
partially and/or replace by Tony's patches before they arrive in mainline.

The current status of my branch is that it works on OMAP5/Pyra but a
quick test on BeagleBone or GTA04 did show some reset/clock errors and
it did not more than creating /proc/pvr. pvrsrvctl --start did fail.

Which means that the omap-pvr-soc-glue patches are currently broken
with 5.3-rc3 anyways...

I'll look at it as soon as possible.

> I've got an AM3517, OMAP35 and a
> DM3730. I am not sure if the AM3517 is even on the radar, but it has
> an sgx530 as well.

Good to know and keep in mind.

BR,
Nikolaus

\
 
 \ /
  Last update: 2019-08-17 11:04    [W:0.147 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site