Quoting Stephen Boyd (2019-07-16 16:47:07) > Quoting Vivek Gautam (2019-06-12 02:26:20) > > > > > > On 6/11/2019 4:51 AM, Stephen Boyd wrote: > > > hardware signal like the NS bit and/or the Execution Level. Hopefully > > > it's a config and then our difference from MTP can be minimized. > > > > I don't think SMMU limits any such programming of SIDs. It's a design > > decision > > to program few SIDs in TZ/Hyp and allocate the corresponding context banks > > and create respective mappings. You should be able to see these SMR > > configurations > > before kernel boots up. I use a simple T32 command - > > > > smmu.add "<name>" <smmu_type> <base_address> > > smmu.streammaptable <name> > > > > e.g. for sdm845 apps_smmu > > > > smmu.add "apps" MMU500 a:0x15000000 > > smmu.StreamMapTable apps > > > > This dumps all the information regarding the smmu. > > Preferably I can see this by using devmem instead of jtag and T32. Do > you know the address of the register? Otherwise I'll go dig into the > documentation and try to figure it out. And this won't really help me will it? I thought the stream ID was "fixed" by hardware, so it seems sort of weird that we're talking about limiting it in TZ/hyp. Here's the S2CR table from Cheza in case that is useful. localhost ~ # mem Welcome to mem interactive mode (featuring python!) Available functions: - r(addr) # Read a single 32-bit word (little endian). - rm(addr, nbytes) # Read memory at the given addr as a string. - w(addr, val) # Write a single 32-bit word (little endian). - wm(addr, val) # Write a string to memory at the given addr. >>> for x in range(64): ... r(0x15000c00 + (x << 2)) ... 0x00000000 0x00000000 0x00000001 0x00000002 0x00000003 0x00000004 0x00000005 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 0x00020000 > > > > > > > > > As far as I can tell, HLOS on SDM845 has always used GPI (yet another > > > DMA engine) to do the DMA transfers. And the GPI is the hardware block > > > that uses the SID of 0x6d6 above, so putting that into iommus for the > > > geniqup doesn't make any sense given that GPI is another node. Can you > > > confirm this is the case? Furthermore, the SID of 0x6c3 sounds untested? > > > Has it ever been generated on SDM845 MTP? > > > > I will get back with this information. > > > > Any update? Any news?
