ChanServ changed the topic of #linux-msm to:
lumag has quit [Ping timeout: 480 seconds]
Danct12 has joined #linux-msm
Danct12 has quit [Quit: Quit]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
dliviu has quit [Ping timeout: 480 seconds]
dliviu has joined #linux-msm
pespin has joined #linux-msm
pevik has quit [Quit: Reconnecting]
pevik has joined #linux-msm
pevik has quit []
pevik has joined #linux-msm
lumag has joined #linux-msm
jhovold has joined #linux-msm
lumag has quit [Ping timeout: 480 seconds]
<calebccff> vkoul: ok, thanks :)
<z3ntu> Hey, I'm struggling to find the "origin" of the iommus value used in the ufs_mem_hc nodes, e.g. https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/qcom/sm8250.dtsi#L2011 and https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/qcom/sdm845.dtsi#L2255 . I just can't find e.g. the 0x4e0 in downstream sources at all or anything that would be an iommu definition. My iommu knowledge is super limited so I might be missing
<z3ntu> something obvious.. Anybody have any suggestion?
<bamse> z3ntu: iirc qualcomm sets up the iommu to do bypass for those from the bootloader, and then they just don't reset the iommu and hope that it all works
pevik has quit [Quit: Lost terminal]
<bamse> z3ntu: so if you dump the smr registers in the arm smmu driver before it clears the registers, you'll typically find usb, ufs and display...and you just need to figure out which is which
<z3ntu> bamse: hm that's useful to know..
jhovold has quit [Ping timeout: 480 seconds]
lumag has joined #linux-msm
pespin has quit [Remote host closed the connection]
cxl000 has quit [Remote host closed the connection]
cxl000 has joined #linux-msm
lumag has quit [Ping timeout: 480 seconds]