Re: [PATCH 5/6] ARM: dts: Configure interconnect target module for omap3 sgx

["H. Nikolaus Schaller" <hns@goldelico.com>]

Hi Adam,

> Am 19.08.2019 um 21:12 schrieb Adam Ford <aford173@gmail.com>:
> 
> On Wed, Aug 14, 2019 at 8:14 AM Tony Lindgren <tony@atomide.com> wrote:
>> 
>> Looks like omap34xx OCP registers are not readable unlike on omap36xx.
>> We use SGX revision register instead of the OCP revision register for
>> 34xx and do not configure any SYSCONFIG register unlike for 36xx.
>> 
>> I've tested that the interconnect target module enables and idles
>> just fine with PM runtime control via sys:
>> 
>> # echo on > $(find /sys -name control | grep \/5000); rwmem 0x5000fe10
>> # rwmem 0x50000014      # SGX revision register on 36xx
>> 0x50000014 = 0x00010205
> 
> For an OMAP3530, I got:
> # echo on > $(find /sys -name control | grep \/5000)
> # devmem 0x50000014
> 0x00010201
> 
> Does 0x00010201 seem reasonable?  I am not sure where to find this in
> the TRM unless it's located elsewhere, but  [1] seems to lead me to
> believe this is correct.

I got on dm3730:

root@letux:~# echo on >/sys/devices/platform/68000000.ocp/5000fe00.target-module/50000000.sgx/power/control
root@letux:~# /usr/bin/arm-linux-gnueabihf/devmem2 0x50000014
/dev/mem opened.
Memory mapped at address 0xb6fc0000.
Value at address 0x50000014 (0xb6fc0014): 0x10205
root@letux:~# 

which indicates ES5.0, as expected for dm3730.

BR,
Nikolaus