[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190817070307.GJ52127@atomide.com>
Date: Sat, 17 Aug 2019 00:03:07 -0700
From: Tony Lindgren <tony@...mide.com>
To: Adam Ford <aford173@...il.com>
Cc: "H. Nikolaus Schaller" <hns@...delico.com>,
Merlijn Wajer <merlijn@...zup.org>,
Paweł Chmiel <pawel.mikolaj.chmiel@...il.com>,
Philipp Rossak <embed3d@...il.com>,
moaz korena <moaz@...ena.xyz>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Filip Matijević <filip.matijevic.pz@...il.com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
linux-omap <linux-omap@...r.kernel.org>,
kernel@...a-handheld.com,
Discussions about the Letux Kernel
<letux-kernel@...nphoenux.org>, maemo-leste@...ts.dyne.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Lay common foundation to make PVR/SGX work without hacks on
OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5
* Adam Ford <aford173@...il.com> [190816 23:02]:
> On Wed, Aug 14, 2019 at 8:16 AM Tony Lindgren <tony@...mide.com> wrote:
> > Well I just posted some sgx interconnect target module patches. We might
> > still have them in v5.4 assuming people manage to review and test them.
>
> 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? 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.
My estimate is am3517 is wired the same way as omap34xx with a 60%
chance, then 30% chance it's wired the same way as omap36xx, and then
10% chance for similar wiring to am335x.. So hopefully that leaves 0%
chance for yet something different for it's wiring :)
If you have a chance please give it a try. Also check the TRM for the
sgx sysconfig register bits to see which of the above matches, and if
3517 has a related rstctrl register like am335x has.
Regards,
Tony
Powered by blists - more mailing lists